Channel
@MefoFuul
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
318subscribers
+16 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003375230211 |
|---|---|
| Type | Channel |
| Username | @MefoFuul |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/MefoFuul |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 09:44 | 318 | +5 |
| 25 Aug 2026, 19:47 | 313 | +7 |
| 19 Aug 2026, 04:47 | 306 | +2 |
| 13 Aug 2026, 05:09 | 304 | +2 |
| 6 Aug 2026, 22:32 | 302 | no change |
| 6 Aug 2026, 12:07 | 302 | first reading |
10 posts held, back to 1 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
221 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 18.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226626125765047275 | 41 | 18.6% | |
| custom 5253846206852902263 | 34 | 15.4% | |
| custom 5210901202522369023 | 29 | 13.1% | |
| custom 5368545906947796103 | 28 | 12.7% | |
| custom 5210764244605239382 | 25 | 11.3% | |
| custom 5453994856827349831 | 19 | 8.60% | |
| custom 5287363410076395965 | 18 | 8.14% | |
| custom 5296511952409885145 | 13 | 5.88% | |
| custom 5424856011984902754 | 8 | 3.62% | |
| custom 5251440286432769524 | 4 | 1.81% | |
| custom 5208560217712788611 | 2 | 0.905% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 10 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 221 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 1 August 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️ ❌❌❌❌❌❌ 🅰️🅰️🅰️🅰️ набор на сигны в Собакине стоимость сигны : 60ру перевод по сбп: 2202208433452100 предзаказ закроется 13.08 в 21:00. Теперь у меня есть свой бот, в который вы можете скидывать скрины перевода вместе со своим ником/псевдо - @Mefooriy_bot Сигны будут высланы в течении 4-х дней.
custom 53685459069477961032custom 52107642446052393821
фанаты подонков еще остались?если хотите мы с кайоши можем отснять ИГОШ.🤩
custom 53685459069477961035custom 54248560119849027543
ухты 2к просмотров.🤩
custom 52109012025223690233
УРА НАС 300¡!!!!¡ я очень рада шо до конца лето мы добили тракториста.🤩 в честь этого,я начерикала свой 2 В ЖИЗНИ артик.
custom 521090120252236902318custom 536854590694779610313custom 521076424460523938211
ЭТО ОЧЕНЬ КРАСИВО
custom 52107642446052393828custom 54248560119849027545
🕊🕊 aya/mitsuki 🕊🕊 PH #risacosp #ayaoosawa #mitsuaya #shucos рт/реакции??
custom 52109012025223690238custom 53685459069477961035custom 52107642446052393823custom 52873634100763959653
через недельку будут новые косплеи,а сейчас я бегаю и глажу бибизян.
custom 522662612576504727512custom 52538462068529022636custom 52873634100763959654custom 53685459069477961033custom 52107642446052393822
коспланы..🤩
custom 522662612576504727514custom 52538462068529022635custom 52514402864327695244custom 54539948568273498313
фото без фш🤩
custom 545399485682734983116custom 528736341007639596511custom 522662612576504727510custom 52538462068529022632
⭐⭐⭐⭐ ⭐⭐⭐⭐ ⭐⭐⭐ meaww🤩
custom 525384620685290226321custom 529651195240988514513custom 52266261257650472755custom 52085602177127886112
Showing the 10 most recent of 10 posts we hold for @MefoFuul. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 5 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 1 September 2026 — this entry's latest reading, not the date you are reading this.
“ηρσɯмαʜ∂σɞʜiκ_123🚷” (@MefoFuul), 318 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/MefoFuul.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.