Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 4 other registered channels. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (2 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 429 comparable posts for this entry, running 4 August 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @chaika_mhl. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 12 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
64 measurements spanning 97 days, net +620. 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 59,849–61,746 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)
Subscribers
Change
10 Nov 2026, 23:09
60,982
-1
9 Nov 2026, 07:50
60,983
-9
7 Nov 2026, 23:10
60,992
+31
6 Nov 2026, 22:16
60,961
-21
6 Nov 2026, 00:46
60,982
-24
5 Nov 2026, 01:29
61,006
-9
3 Nov 2026, 23:38
61,015
-32
3 Nov 2026, 00:11
61,047
-79
1 Nov 2026, 22:47
61,126
-102
31 Oct 2026, 22:51
61,228
-93
30 Oct 2026, 22:06
61,321
-206
29 Oct 2026, 23:46
61,527
+169
28 Oct 2026, 22:57
61,358
+277
27 Oct 2026, 22:44
61,081
+92
26 Oct 2026, 20:17
60,989
+26
25 Oct 2026, 19:45
60,963
-6
24 Oct 2026, 18:41
60,969
+9
23 Oct 2026, 15:10
60,960
+157
22 Oct 2026, 11:44
60,803
+31
21 Oct 2026, 01:37
60,772
first reading
Engagement
1,149 posts held, back to 4 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 197 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
10.7%
avg views ÷ 60,982 subscribers
Avg views / post
6,540
345 posts measured
Reaction rate
3.55%
reactions ÷ views · ER floor
Posts in window
345
of 1,149 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 11 November 2026
Posts held
1,149 (4 August 2026 – 11 November 2026)
Views total
2,254,587
Reactions total
80,076
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 23:54 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
≈17,700
Videos
≈5,240
Links
≈4,790
Lifetime counters from Telegram’s own channel header, read 11 November 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
5h 25m
Average length
53s
Measured directly from 370 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
248,467 reactions across 1,000 posts, in 16 distinct kinds. The most used accounts for 48.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
120,007
48.3%
custom 5215383752515025101
69,250
27.9%
🔥
32,634
13.1%
😭
6,628
2.67%
🤣
4,902
1.97%
😢
4,195
1.69%
🏆
3,182
1.28%
👏
2,130
0.857%
🎉
1,760
0.708%
😁
1,112
0.448%
👀
694
0.279%
🐳
497
0.2%
🤔
465
0.187%
🤩
410
0.165%
🙊
340
0.137%
😎
261
0.105%
Custom emoji. One 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 count beside it is 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 1,000 of the 1,000 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 248,467 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 26 August 2026 to 11 November 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.
Telegram Stars
Stars received
245
across the posts below
Posts paid on
100
of 1,000 we hold a reading for · 10%
Most on one post
105
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @torpedonn. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 26 August 2026 to 11 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
Ad load
0.1%
1 of 1,000 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
5,480
over 1 measured post
Median views · rest
6,340
over 999 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2W5zFHQ43NH
1
23 October 2026
23 October 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 26 August 2026 to 11 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 44 of 345 posts held from the last 30 days (12.8%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Защитник Скутер Брики, подводя итоги после матча с ЦСКА, порассуждал о том, какие уроки может извлечь команда из таких игр, как сегодня, а также над чем конкретно стоит поработать, чтобы улучшить результат 👏
Верим в команду! Начался второй период 👏
🐴4️⃣↔️0️⃣🦌
❤101🤣50custom 521538375251502510146🏆19😭14🙊12😁2👀1
Showing the 12 most recent of 1,149 posts we hold for @torpedonn. 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.
Posts edited after publishing
@torpedonn edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
25 August 2026
Most recent edit
21 October 2026
Posts recorded as deleted after publishing
We recorded 1 post on @torpedonn as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
9 October 2026
Most recent seen missing
9 October 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
0
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 49 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 37 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 22 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
ЧЕРКАС АТЛАНТ @cherkasatlant · 49,690 Telegram ranks this channel #4 of 95 here — alongside 94 others — read 25 August 2026
ХК «Спартак» Москва @hc_spartak · 60,983 Telegram ranks this channel #5 of 99 here — alongside 98 others — read 22 August 2026
Молодежная хоккейная лига I МХЛ @mhlrus · 49,609 Telegram ranks this channel #6 of 99 here — alongside 98 others — read 25 August 2026
ХК ЦСКА Москва @cska_hockey · 48,793 Telegram ranks this channel #7 of 97 here — alongside 96 others — read 26 August 2026
Анжелика Стубайло @Astubailo · 19,737 Telegram ranks this channel #8 of 97 here — alongside 96 others — read 28 September 2026
Хоккейный клуб СКА @hcska · 52,902 Telegram ranks this channel #8 of 99 here — alongside 98 others — read 25 August 2026
Хоккейный клуб «Локомотив» @hclokomotiv_official · 80,307 Telegram ranks this channel #8 of 86 here — alongside 85 others — read 18 August 2026
Волчья стая. Канал ХК "Нефтехимик" @wolfstaya · 22,053 Telegram ranks this channel #9 of 81 here — alongside 80 others — read 22 September 2026
Хоккей России @rusicehockey · 28,100 Telegram ranks this channel #10 of 95 here — alongside 94 others — read 10 September 2026
ХК Северсталь @hcseverstal · 29,694 Telegram ranks this channel #10 of 79 here — alongside 78 others — read 8 September 2026
Роман с Хоккеем @hockeywithroman · 58,113 Telegram ranks this channel #10 of 98 here — alongside 97 others — read 23 August 2026
Матч! Хоккей @hockey_match · 57,071 Telegram ranks this channel #10 of 98 here — alongside 97 others — read 22 August 2026
ХОККЕЙ ЗБС 🏒 @hockeyzbz · 51,374 Telegram ranks this channel #11 of 88 here — alongside 87 others — read 24 August 2026
ХК «Ак Барс» @hc_akbars · 122,585 Telegram ranks this channel #11 of 90 here — alongside 89 others — read 13 August 2026
ХК "Адмирал" @hcadmiralru · 35,751 Telegram ranks this channel #12 of 92 here — alongside 91 others — read 2 September 2026
ХК «Металлург» @metallurgmgn · 60,664 Telegram ranks this channel #12 of 71 here — alongside 70 others — read 22 August 2026
ВХЛ @vhl_src · 40,413 Telegram ranks this channel #14 of 100 here — alongside 99 others — read 30 August 2026
ХК «Трактор» | Челябинск @hctraktor · 104,878 Telegram ranks this channel #14 of 83 here — alongside 82 others — read 15 August 2026
Территория Тигров | ХК «Амур» @hcamur1957 · 33,123 Telegram ranks this channel #15 of 86 here — alongside 85 others — read 5 September 2026
ХК «Сибирь» @hockeyclubsibir · 90,218 Telegram ranks this channel #15 of 88 here — alongside 87 others — read 17 August 2026
Роганов Хоккей @roganov_hockey · 67,039 Telegram ranks this channel #16 of 98 here — alongside 97 others — read 20 August 2026
ХК Динамо Минск | HC Dinamo Minsk 🐂 @hcdinamoby · 84,642 Telegram ranks this channel #16 of 98 here — alongside 97 others — read 18 August 2026
Путь Дракона | Шанхай Дрэгонс @shadragons · 32,676 Telegram ranks this channel #17 of 96 here — alongside 95 others — read 4 September 2026
Хоккейные Сливки @hockey_slivki · 32,991 Telegram ranks this channel #17 of 96 here — alongside 95 others — read 4 September 2026
This channel appears in 88 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cross-platform identity — Wikidata
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“ХК Торпедо” (@torpedonn), 60,982 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/torpedonn.
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.
