Telegram RegisterThe public register of Telegram

Channel

ˏ » 𝓘nf𝓸 𝓜FF

@infochannelMFF

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

43subscribers

+0 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003669271072
TypeChannel
Username@infochannelMFF
Description⌗ 𝙞𝙣𝙛𝙤 — 𝙛𝙡𝙤𝙤𝙙: 𝙢𝙞𝙣𝙚𝙘𝙧𝙖𝙛𝙩 𝙛𝙖𝙣𝙙𝙤𝙢𝙨. здесь находится основная информация о нашем флуде ! лайф : . @MFFlife ✎
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/infochannelMFF

Growth

4312 Aug 2026, 21:48 — 43 subscribers12 Aug 2026, 22:01 — 43 subscribers12 Aug 2026, 21:4812 Aug 2026, 22:01
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 42–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:0143no change
12 Aug 2026, 21:4843first reading

Engagement

20 posts held, back to 5 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
261.6%
avg views ÷ 43 subscribers
Avg views / post
113
2 posts measured
Reaction rate
1.74%
reactions ÷ views · ER floor
Posts in window
2
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 July 2026
Posts held20 (5 June 202625 July 2026)
Views total225
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 22:01 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
6
Links
4

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

28 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍾725.0%
🕊621.4%
🆒517.9%
🏆414.3%
🎉310.7%
🔥310.7%

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 20 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 28reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 5 June 2026 to 25 July 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.

Recent posts

25 Jul 2026, 11:18 UTC115 views2 reactionsread 12 August 2026
Photo

︎𖫲♡ ︎ ︎ ︎ ⎯ ︎ ︎ ︎ ︎𝓒овсем недавно. . 𝆬 ㅤ𝆹𝅥 𝐟᳢𝟓 ⁠⁠ ⁠⁠⁠᷼︵ㅤ۪ 𝓨 нас был заключён ⁠⁠⁠ ⁠⁠⁠𝓖᪾𝜚 𐑺︩︪𝆬 ׄ дружеский союз ! ɞ ִ ㅤ ݂ㅤ ‌︶ㅤ𓆩 𝓡ainbo𝔀 𝓦e𝓫. ۫ 𓆪 ׅ ︵᷼⏜ 愛⸝⸝ & 𝓜FF ׄ᷼ ˖ ྀㅤ︶ ׄ 𝔀ith lov𝓮ˏ ִ 氷 ˎ 我 ݂ 𝓑ладельцы — @sannohate 𝓷 @invenli . ׄ 𖧁 𝅄 ׄ

🔥1🆒1

5 Jun 2026, 13:25 UTC402 views5 reactionsread 12 August 2026
Photo

. ┄ 𝓑сех пр𝓾ветствуе𝓜 на 𝓞ткрыт𝓾и нашего л𝓪йф-ка𝓗ала ! ! '≪ ╹тут б𝔂дет пос𝓣иться «ж𝓾знь» . ︽ 𖥻 наш𝓔го фл𝔂да. ╻ ꒷꒦ // и𝓷терактивы, конку𝓹сы, 𝓑ид𝓮о, важ𝓗ая инф𝓸рмация, . . и т.д. ⇗⇗ всё эт𝓸 буд𝓔т тут. д𝓐 ! ! ︾

🕊3🍾2

5 Jun 2026, 13:24 UTC398 views6 reactionsread 12 August 2026
Photo

>> . . « 𝔂 нашего 𝓕луда появ𝓾лся св𝓸й 𝓜айн 𝓒ерве𝓹.! » ,* '' ⦅ за н𝓮го отве𝓻ает н𝓪ш 𝓐дмин 𝓢𝓱arpnes𝒔 . [ 𖥻 ˏdedlnsaid и . . ] . ⦆ участник ⌗ ˏ𝓜ark ! ! 𝓲𝓕 вас 𝓮то могло за𝓾нтере𝓸овать, то 𝓜ожете 𝓗аписать и𝓶 ↑ з𝓪 под𝓹обн𝓸стям𝓾. . '๑ , ᯓ ܀ ♯. .彡 ⊹˚⌑

🏆4🍾2

5 Jun 2026, 13:23 UTC362 views3 reactionsread 12 August 2026
Photo

ˊ ⤹ .𝓒leaning𝓼 . ꒰ ˏ𔓕 ꒱ ˏ 𝓢истки проводятся каждое воскресенье в неопределенное время . ˎ 𝓗орма — 80 сообщений в неделю ˒˓ ˏ 𝓗ью ⦅ участники, находящиеся во флуде 1 - 5 дней ⦆ не участвуют в чистках . ˎ 𝓑 случае, если вы наберёте менее 30 - ти сообщений — бан ˒˓ ⸕ . ۫ ֹ ܻ ⸝⸝

🕊3

5 Jun 2026, 13:23 UTC333 views2 reactionsread 12 August 2026

ˏ 𝓡ule𝓼 —— ! *•‌‌ .•‌‌‌*˚ `•.° - .•‌‌‌ ' . . • ʜϱ ʒʜαʜυϱ ηραɞυⲗ ʜϱ σсɞσɓσж∂αϱτ ɞαс στ στɞϱτсτɞϱʜʜσсτυ. ⦅ 1 ⦆ — 𝓗е оскорблять участников, администрацию, их родословную и т.п. ( разрешается лишь в виде шутки/если сам человек не против ) 𝓗аказание . . варн и/или мут два часа !! ⦅ 2 ⦆ — 𝓟екламировать тгк, флуды, ролки и остальное можно лишь с разрешения владельца. 𝓗аказание . . варн и/и

🎉2

5 Jun 2026, 13:22 UTC341 views2 reactionsread 12 August 2026
Photo

〢 ╷ .𝓐dministratio𝓷 ╵ ⋊ ⸔ ›› 𝓞wne𝓻 & 𝓒ᴏ - 𝓞wne𝓻 . — 𝓒lownPierceˏ 𝓔ggchan — @invenli / влд. — 𝓢kratch — @SINKVV11 / совлд. ➥ следят за порядком в чатеˏ ищат ньюˏ улучшают флуд ˏ его комфортабельность и т.д. ·˚ ༘₊ ›› 𝓐dmi𝓷 𝓕o𝓻 𝓝e𝔀 . — 𝓢asha — @fish66889 ✶ ➥ принимает ньюˏ следит за чатом и инфо, делает интерактивы. ·˚ ༘₊ ›› 𝓐dministrator𝓼 . — 𝓢harpness — @dedlnsaid

🔥2

Showing the 12 most recent of 20 posts we hold for @infochannelMFF. 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.

Citation-graph rank

Citation-graph rank — 145,455 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 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.

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.

Cite this entry

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“ˏ » 𝓘nf𝓸 𝓜FF” (@infochannelMFF), 43 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/infochannelMFF.

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.