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 20 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Growth
59 measurements spanning 92 days, net -445. 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 61,830–62,668 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)
Subscribers
Change
6 Nov 2026, 17:07
61,954
-8
5 Nov 2026, 15:26
61,962
+35
4 Nov 2026, 12:36
61,927
-20
3 Nov 2026, 09:36
61,947
-13
2 Nov 2026, 12:17
61,960
-40
1 Nov 2026, 14:31
62,000
-21
31 Oct 2026, 13:38
62,021
-5
30 Oct 2026, 11:50
62,026
-78
29 Oct 2026, 10:45
62,104
-58
28 Oct 2026, 06:18
62,162
-15
27 Oct 2026, 06:29
62,177
+10
26 Oct 2026, 07:15
62,167
-35
25 Oct 2026, 07:06
62,202
-32
24 Oct 2026, 05:00
62,234
-65
23 Oct 2026, 02:38
62,299
-5
22 Oct 2026, 00:10
62,304
+47
20 Oct 2026, 15:46
62,257
+68
19 Oct 2026, 18:47
62,189
+33
18 Oct 2026, 18:56
62,156
+19
17 Oct 2026, 15:21
62,137
first reading
Engagement
1,358 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 195 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
26.9%
avg views ÷ 61,954 subscribers
Avg views / post
16,700
488 posts measured
Reaction rate
1.70%
reactions ÷ views · ER floor
Posts in window
488
of 1,358 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 7 November 2026
Posts held
1,358 (4 August 2026 – 7 November 2026)
Views total
8,137,350
Reactions total
138,398
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Nov 2026, 10:52 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
≈26,500
Videos
≈258
Links
≈163
Lifetime counters from Telegram’s own channel header, read 7 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
6m 22s
Average length
21s
Measured directly from 18 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
261,900 reactions across 1,000 posts, in 41 distinct kinds. The most used accounts for 18.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
49,327
18.8%
⚡
44,454
17.0%
🔥
42,532
16.2%
🤣
37,362
14.3%
🤯
25,130
9.60%
👏
10,221
3.90%
❤🔥
8,587
3.28%
👎
6,893
2.63%
🎉
5,116
1.95%
😢
4,455
1.70%
😁
3,760
1.44%
😭
3,478
1.33%
🤔
2,737
1.05%
☃
2,725
1.04%
😱
1,737
0.663%
🤬
1,731
0.661%
😨
1,558
0.595%
🏆
1,311
0.501%
🤪
1,157
0.442%
💯
999
0.381%
21 further kinds
6,630
2.53%
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 261,900 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 7 September 2026 to 7 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
98
across the posts below
Posts paid on
72
of 1,000 we hold a reading for · 7%
Most on one post
6
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @transfers_khl. 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 7 September 2026 to 7 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
9,670
over 1 measured post
Median views · rest
16,300
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
2W5zFHCBJsC
1
30 October 2026
30 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 7 September 2026 to 7 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: 24 of 488 posts held from the last 30 days (4.92%) 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).
У этой джерси сразу два ответа на вопрос, кто настоящие хозяева Сибири
PARI выпустила новый дроп к дерби «Авангарда» и «Сибири»: ястреб и снеговик заняли разные рукава, а на груди появилась надпись «Хозяева Сибири». На спине — арены обоих соперников и хоккей с сибирским колоритом: коньки-валенки, клюшки с ведрами и ястреб в теплом (надеемся) платке.
В какой сектор идти в такой джерси — еще один повод для спора межд…
🚙 1:0 (БУЛ) 🚂 Тольяттинская «Лада» второй раз в сезоне одержала «сухую» победу над «Локомотивом».
🤣531🎉154❤🔥35👍18🤯10👏9🔥8👎6
Showing the 12 most recent of 1,358 posts we hold for @transfers_khl. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@transfers_khl 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
9 September 2026
Most recent edit
13 September 2026
Posts recorded as deleted after publishing
We recorded 7 posts on @transfers_khl 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 August 2026
Most recent seen missing
25 October 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
1
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 9 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.
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 21 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.
КХЛ @khl_official_telegram · 284,026 Telegram ranks this channel #1 of 98 here — alongside 97 others — read 10 August 2026
Только Хоккей l Трансферы КХЛ @Only_Hockey1 · 24,286 Telegram ranks this channel #2 of 97 here — alongside 96 others — read 15 September 2026
НХЛ | NHL | Национальная Хоккейная Лига @nhlvk · 85,907 Telegram ranks this channel #2 of 99 here — alongside 98 others — read 18 August 2026
Путь Дракона | Шанхай Дрэгонс @shadragons · 32,726 Telegram ranks this channel #4 of 96 here — alongside 95 others — read 4 September 2026
Хоккейные Сливки @hockey_slivki · 33,052 Telegram ranks this channel #4 of 96 here — alongside 95 others — read 4 September 2026
ХК "Адмирал" @hcadmiralru · 35,650 Telegram ranks this channel #4 of 92 here — alongside 91 others — read 2 September 2026
Роман с Хоккеем @hockeywithroman · 58,200 Telegram ranks this channel #4 of 98 here — alongside 97 others — read 23 August 2026
ХК «Динамо» Москва | HC Dynamo Moscow @dynamo_ru · 45,489 Telegram ranks this channel #5 of 99 here — alongside 98 others — read 27 August 2026
ХОККЕЙ ЗБС 🏒 @hockeyzbz · 51,357 Telegram ranks this channel #5 of 88 here — alongside 87 others — read 24 August 2026
Матч! Хоккей @hockey_match · 57,101 Telegram ranks this channel #5 of 98 here — alongside 97 others — read 22 August 2026
PRO наш Хоккей 🇷🇺 @hockey_vbros · 252,731 Telegram ranks this channel #5 of 96 here — alongside 95 others — read 15 August 2026
ХК «Авангард» Омск 🦅 @omskiyavangard · 327,101 Telegram ranks this channel #5 of 93 here — alongside 92 others — read 10 August 2026
Территория Тигров | ХК «Амур» @hcamur1957 · 33,138 Telegram ranks this channel #6 of 86 here — alongside 85 others — read 5 September 2026
Хайруллин Live @tebevukhokriknut · 40,325 Telegram ranks this channel #6 of 94 here — alongside 93 others — read 30 August 2026
Роганов Хоккей @roganov_hockey · 67,009 Telegram ranks this channel #6 of 98 here — alongside 97 others — read 20 August 2026
Молодежная хоккейная лига I МХЛ @mhlrus · 49,681 Telegram ranks this channel #7 of 99 here — alongside 98 others — read 25 August 2026
ХК «Металлург» @metallurgmgn · 60,754 Telegram ranks this channel #7 of 71 here — alongside 70 others — read 22 August 2026
🏒 ШТАБ ХОККЕИСТА @one_hockey · 80,042 Telegram ranks this channel #7 of 97 here — alongside 96 others — read 19 August 2026
Roman Rotenberg 🇷🇺 @rotenberg81 · 148,885 Telegram ranks this channel #7 of 99 here — alongside 98 others — read 12 August 2026
ХК ЦСКА Москва @cska_hockey · 48,696 Telegram ranks this channel #8 of 97 here — alongside 96 others — read 26 August 2026
Atributika&Club @atributikaclub · 25,923 Telegram ranks this channel #9 of 96 here — alongside 95 others — read 12 September 2026
Правый хват/Михаил Зислис @Righthanded78 · 26,579 Telegram ranks this channel #9 of 95 here — alongside 94 others — read 12 September 2026
АренаБреда @arena_breda · 31,004 Telegram ranks this channel #9 of 96 here — alongside 95 others — read 6 September 2026
Селекционный отдел @hockeyscout · 18,958 Telegram ranks this channel #10 of 77 here — alongside 76 others — read 4 October 2026
This channel appears in 71 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.
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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“Трансферы КХЛ | ХОККЕЙ” (@transfers_khl), 61,954 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/transfers_khl.
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.
