Telegram RegisterThe public register of Telegram

Channel

Steel Fox | ХК «Металлург» Магнитогорск

@sf_mmg

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

11,826subscribers

-44 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001494565924
TypeChannel
Username@sf_mmg
DescriptionАвторский блог болельщика о магнитогорском «Металлурге»: новости, мнения, эмоции, разборы и всё, чем живёт фанат команды. 💬 Связь - @record9
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged2 times, most recently 14 August 2026
On Telegramt.me/sf_mmg

Growth

11,82611,87011,8487 August 2026 — 11,870 subscribers7 August 2026 — 11,870 subscribers8 August 2026 — 11,862 subscribers9 August 2026 — 11,857 subscribers10 August 2026 — 11,851 subscribers11 August 2026 — 11,841 subscribers12 August 2026 — 11,832 subscribers13 August 2026 — 11,826 subscribers7 August 202613 August 2026
8 measurements spanning 6 days, net -44. 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 11,819–11,877 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:5511,826-6
12 Aug 2026, 07:2311,832-9
11 Aug 2026, 08:5711,841-10
10 Aug 2026, 10:0211,851-6
9 Aug 2026, 10:5111,857-5
8 Aug 2026, 08:3611,862-8
7 Aug 2026, 09:3011,870no change
7 Aug 2026, 09:2111,870first reading

Engagement

61 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
19.0%
avg views ÷ 11,826 subscribers
Avg views / post
2,250
61 posts measured
Reaction rate
3.27%
reactions ÷ views · ER floor
Posts in window
61
of 61 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
WindowRolling 30 days · latest post in window 14 August 2026
Posts held61 (2 August 202614 August 2026)
Views total137,242
Reactions total4,483
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 02:11 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
4,520
Videos
947
Links
1,110

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
18m 45s
Average length
1m 15s

Measured directly from 15 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

4,483 reactions across 61 posts, in 41 distinct kinds. The most used accounts for 42.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,91042.6%
custom 540884580842446792745710.2%
custom 52041246589573209734259.48%
🔥3658.14%
👍2525.62%
❤‍🔥1583.52%
😢1373.06%
🤣992.21%
custom 5325880328894554534741.65%
🤝681.52%
😨601.34%
custom 5204160139682151714491.09%
😭491.09%
custom 4981038280872035186430.959%
🤨400.892%
🌚380.848%
💋380.848%
💘300.669%
🥱260.58%
👎190.424%
21 further kinds1463.26%

Custom emoji. 5 of the rows above are 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 areTelegram’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 61 of the 61 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 4,483reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 61 most recent posts we hold, published 2 August 2026 to 14 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.

Recent posts

14 Aug 2026, 18:02 UTC932 views42 reactionsread 15 August 2026
Video

Мысли после матча с Драконами 🦊🔥 – про новичков – про Заврагина – про Яковлева – про большинство 🦊 | @sf_mmg

25👍8custom 52041246589573209735🔥4

14 Aug 2026, 16:47 UTC≈1,230 views26 reactionsread 15 August 2026

⚡️ Лучшие игроки матча? Кто понравился по итогу вам сегодня? 🦊 | @sf_mmg

💋215

14 Aug 2026, 16:40 UTC≈1,310 views28 reactionsread 15 August 2026

Знаете, что меня немного смущает – время матча 🦊 Металлург - 🦬 Динамо Минск ВО СКОЛЬКО ВСЕ-ТАКИ МАТЧ? Кинопоиск пишет, что мы днем играем, а в расписании в 19:00…

28

14 Aug 2026, 16:35 UTC≈1,360 views45 reactionsread 15 August 2026
Photo

Ну и традиционно перебросали соперника аж в три раза 👀🔥 🦊 | @sf_mmg

27💋10custom 54088458084244679276🔥2

14 Aug 2026, 16:15 UTC≈1,420 views48 reactionsread 15 August 2026
Photo

🦊 Металлург в овертайме вырывает победу у 🐉 «Шанхай Дрэгонс» в матче Кубка Минска 1:0. 21’. Паливко (Коробкин, Сиряцкий) 2:2. 58’. Зеленов (Вовченко, Толчинский) 3:2. 63’. Нечаев (буллит) 🦊 | @sf_mmg

46💋2

14 Aug 2026, 15:24 UTC≈1,710 views94 reactionsread 15 August 2026
Photo

🔥🔥🔥 ПОБЕЕЕЕЕЕЕДА 3:2 ОТ. Нечаев (буллит) 🦊 Металлург – 🐉 Драконы 🦊 | @sf_mmg

custom 52041246589573209737417🔥3

14 Aug 2026, 15:11 UTC≈1,680 views58 reactionsread 15 August 2026

ГООООООООЛ 2:2. Зеленов!

50custom 52041246589573209738

14 Aug 2026, 14:32 UTC≈1,750 views29 reactionsread 15 August 2026

2-й период завершен! 1:1 у нас. Заскучали?

🥱263

14 Aug 2026, 14:13 UTC≈1,800 views66 reactionsread 15 August 2026

1:2 Драконы выходят вперед UPD. Отмена! 1:1

🤨40custom 540884580842446792722❤‍🔥4

14 Aug 2026, 13:59 UTC≈1,810 views23 reactionsread 15 August 2026

Металлург добавил в скоростях и Драконы стали ошибаться

❤‍🔥20custom 52041601396821517143

14 Aug 2026, 13:41 UTC≈1,850 views25 reactionsread 15 August 2026

По нулям после первого. Кого бы отметили из игроков по первому отрезку?

❤‍🔥24👎1

14 Aug 2026, 13:00 UTC≈1,860 views92 reactionsread 15 August 2026
Photo

🔥 Егор Коробкин – капитан на матч с Драконами 🦊 | @sf_mmg

👍6414custom 532567474598998713711❤‍🔥3

Showing the 12 most recent of 61 posts we hold for @sf_mmg. 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 — 387,920 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.

Forward network

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

“Steel Fox | ХК «Металлург» Магнитогорск” (@sf_mmg), 11,826 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/sf_mmg.

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.