Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 8 October 2026 and assigned it the closest of 31 fixed categories, at 84% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
4 measurements spanning 19 days, net +4. 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 44–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Oct 2026, 00:59
49
-1
28 Sept 2026, 03:37
50
+5
18 Sept 2026, 17:22
45
no change
18 Sept 2026, 16:47
45
first reading
Engagement
8 posts held, back to 13 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.
ERR · 30 days
49.0%
avg views ÷ 49 subscribers
Avg views / post
24.0
2 posts measured
Reaction rate
14.6%
reactions ÷ views · ER floor
Posts in window
2
of 8 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 18 September 2026
Posts held
8 (13 August 2026 – 18 September 2026)
Views total
48
Reactions total
7
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
18 Sept 2026, 17:22 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.
Reaction mix
82 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 22.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5231126555706560414
18
22.0%
custom 5418340276013926579
18
22.0%
custom 5415659881413773414
16
19.5%
custom 5415769458914396977
16
19.5%
custom 5415606168552770097
14
17.1%
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 7 of the 8 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 82 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 13 August 2026 to 18 September 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.
🌟🌟🌟🌟🤩 полночь, когда луна
🌟🌟🌟🌟🤩красилась в цвет
🌟🌟🌟🌟🤩апёкшейся крови, в
🌟🌟🌟🌟🤩ревнем подземном зале
🌟🌟🙂обрались те, чья жизнь — вечная жажда. Чаша из чёрного обсидиана приняла алые капли, и над ней прозвучала клятва на крови, произнесённая шёпотом теней. Каждый, кто коснулся края чаши, оставил в ней не только кровь, но и обещание не поднимать руку на брата по ночи.
Так был заключён нерушимый союз, скреплённый не черни…
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
ⲙᥲ᥎ιᥒ᥉
наша прекрасная семья находится в поиске союзов
🤩папки — рп/вз/рп+актив
🤩следящие — @wvv380 , @Dark_Ang4l
🤩для тех у кого бан — @kerrluin4bot
🤩допы — 2:2-5:5
💕💕💕💕💕💕💕💕💕💕💕💕
🔤υʅҽʂ.
1. уважайте администрацию, участников и правила сообщества.
не соблюдение правил — пред или мут
2. не вызывать калл без острой обходимости.
если по приколу варн или словесное предупреждение
3. нот вирт принимаем (запрещено отправлять кружки, фото лица, гс в чат, но можно всякие фото/видео/кружки где не видно вашего лица)
4. контент 18+ разрешен, но должен быть умеренным.
5. оскорбление религий — бан.
6. е…
🔤คtēຖt
🔤азвание "Mavins" официально присваиваем себе.
Права на это название послностью принадлежит только этой кф. В случае кражи/байта вы нарушете авторское право и автоматически признаёте себя плагиатчиком без собственного вкуса. Повторное изспользование названия третьими лицами запрещены.
Showing the 8 most recent of 8 posts we hold for @mmavins. 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.
Forward network
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.
Mentions
Named by 1 registered channel — 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.
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 8 October 2026 — this
entry's latest reading, not the date you are reading this.
“ⲙᥲ᥎ιᥒ᥉ ιᥒ𐔥𐔖.” (@mmavins), 49 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/mmavins.
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.
