Telegram RegisterThe public register of Telegram
Telegram profile photo for PROХоккей | КХЛ NHL ТРАНСФЕРЫ

Channel

PROХоккей | КХЛ NHL ТРАНСФЕРЫ

@khokkeyi

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

31,700subscribers

-132 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001721004875
TypeChannel
Username@khokkeyi
Description🏒 Эксклюзивные новости, инсайды, аналитика: всё самое важное из мира хоккея в одном канале Сотрудничество: @hokck
Created30 December 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/khokkeyi

Topic

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 10 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 why it has no browse page of its own yet.

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 word for word on 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hockeyonkp/354066 Aug 2026, 18:39 UTC@khokkeyi/9350 · this entry7 Aug 2026, 04:45 UTC0.9810 hours
@hockeyonkp/353823 Aug 2026, 17:54 UTC@khokkeyi/9337 · this entry4 Aug 2026, 05:41 UTC0.9812 hours
@hockeyonkp/353864 Aug 2026, 13:02 UTC@khokkeyi/9338 · this entry4 Aug 2026, 13:38 UTC0.9836 minutes
@hockeyonkp/353925 Aug 2026, 11:04 UTC@khokkeyi/9342 · this entry5 Aug 2026, 11:49 UTC0.9645 minutes
@hockeyonkp/353884 Aug 2026, 16:51 UTC@khokkeyi/9340 · this entry5 Aug 2026, 01:05 UTC0.958.2 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@hockeyonkp5 (5/5 hand-verifiable sample passed)0.978.2 hours@hockeyonkp (50)

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. 1 of the 5 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 21 comparable posts for this entry, running 3 August 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @hockeyonkp. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

Growth

31,70031,83231,7667 August 2026 — 31,832 subscribers8 August 2026 — 31,830 subscribers9 August 2026 — 31,827 subscribers10 August 2026 — 31,823 subscribers11 August 2026 — 31,819 subscribers12 August 2026 — 31,813 subscribers12 August 2026 — 31,806 subscribers14 August 2026 — 31,801 subscribers15 August 2026 — 31,796 subscribers17 August 2026 — 31,790 subscribers18 August 2026 — 31,776 subscribers19 August 2026 — 31,774 subscribers20 August 2026 — 31,765 subscribers21 August 2026 — 31,762 subscribers22 August 2026 — 31,761 subscribers24 August 2026 — 31,755 subscribers25 August 2026 — 31,753 subscribers26 August 2026 — 31,741 subscribers27 August 2026 — 31,746 subscribers28 August 2026 — 31,737 subscribers29 August 2026 — 31,731 subscribers30 August 2026 — 31,726 subscribers31 August 2026 — 31,724 subscribers1 September 2026 — 31,714 subscribers2 September 2026 — 31,711 subscribers3 September 2026 — 31,707 subscribers5 September 2026 — 31,700 subscribers7 August 20265 September 2026
27 measurements spanning 30 days, net -132. 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 31,680–31,852 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
5 Sept 2026, 23:2231,700-7
3 Sept 2026, 19:0031,707-4
2 Sept 2026, 09:0331,711-3
1 Sept 2026, 10:4631,714-10
31 Aug 2026, 11:5931,724-2
30 Aug 2026, 12:0331,726-5
29 Aug 2026, 09:0731,731-6
28 Aug 2026, 12:2331,737-9
27 Aug 2026, 12:2431,746+5
26 Aug 2026, 14:2431,741-12
25 Aug 2026, 14:4231,753-2
24 Aug 2026, 13:3731,755-6
22 Aug 2026, 23:2931,761-1
21 Aug 2026, 10:4531,762-3
20 Aug 2026, 11:3831,765-9
19 Aug 2026, 11:1531,774-2
18 Aug 2026, 09:1231,776-14
17 Aug 2026, 10:0831,790-6
15 Aug 2026, 17:5731,796-5
14 Aug 2026, 04:4831,801first reading

Engagement

144 posts held, back to 3 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 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.81%
avg views ÷ 31,700 subscribers
Avg views / post
257
113 posts measured
Reaction rate
0.753%
reactions ÷ views · ER floor
Posts in window
115
of 144 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 51 of 113 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 7 September 2026
Posts held144 (3 August 20267 September 2026)
Views total29,011
Reactions total101
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Sept 2026, 13:12 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
3,440
Videos
4,910
Links
7,330

Lifetime counters from Telegram’s own channel header, read 7 September 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
17m 48s
Average length
24s

Measured directly from 45 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

127 reactions across 58 posts, in 8 distinct kinds. The most used accounts for 33.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4333.9%
👍3829.9%
🔥2822.0%
🤡64.72%
😁53.94%
👎43.15%
🤬21.57%
😎10.787%

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

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

Recent posts

7 Sept 2026, 11:04 UTC90 views1 reactionsread 7 September 2026
Video

🕯 Большая трагедия случилась 15 лет назад… Каждая победа, каждый кубок — ради них. Ребята, мы помним 🕊 🏒 PROХоккей

1

7 Sept 2026, 09:44 UTC108 viewsread 7 September 2026
Photo

🔥 Восемь матчей — большущий игровой день в Лиге! 🔸«Авангард» откроет сезон встречей с «Салаватом». 🔹В Екатеринбурге состоится первое Уральское дерби в регулярке. 🔹Продолжит ли «Сибирь» победную серию из пяти матчей над «Барысом»? 🔹Обе команды стартовали с поражений. Кто наберёт два очка в Череповце? 🔹В Минске готовятся к приезду «Торпедо» с молодыми звёздочками. 🔹«Адмирал» дебютирует в сезоне матчем против фина

7 Sept 2026, 03:08 UTC171 views5 reactionsread 7 September 2026
Video

👑 КОРОЛЬ ПЯТАКА СНОВА В ДЕЛЕ! Дмитрий Яшкин принёс своей новой команде победу в овертайме — он переправил шайбу с лёта после наброса Бреннана Менелла. Очень важный гол в первом же матче за «Драконов» 🔥 🏒 PROХоккей

2👍2🔥1

6 Sept 2026, 16:43 UTC212 views1 reactionsread 7 September 2026
Photo

🏒 А «ДРАКОНЫ»-ТО С ХАРАКТЕРОМ! Два раза смогли отыграться в гостях у «Нефтехимика», а в овертайме вообще вырвали победу. За такой матч парням Митча Лава ❤️ 🏒 PROХоккей

👍1

6 Sept 2026, 16:20 UTC201 viewsread 7 September 2026
Video

🏒🏒🏒 «ДРАКОНЫ» ОТЫГРЫВАЮТСЯ С 0:3! 🏒 PROХоккей

6 Sept 2026, 15:22 UTC193 viewsread 7 September 2026
Video

😱 За одно удаление Хоружева команды забили дважды Сначала игроки «Нефтехимика» в меньшинстве реализовали контратаку, а потом уже «Драконы» всё-таки использовали численное преимущество. 🏒 PROХоккей

6 Sept 2026, 15:01 UTC193 viewsread 7 September 2026
Video

👊 Надворный и в новом сезоне не даёт соперникам расслабиться Дмитрий Яшкин уже прочувствовал это на себе: жёстко ответил на силовой приём Матвея и заработал две минуты штрафа. Будем ждать продолжения этого противостояния 🔥 🏒 PROХоккей

6 Sept 2026, 14:16 UTC191 viewsread 7 September 2026
Video

А про пятак «Драконы» совсем забыли 🤷‍♂️ Партнёры нашли Никиту Хоружева, и он мгновенно использовал момент. А Виктор Андрейченко отдал ассист в своём первом матче в лиге. 🏒 PROХоккей

6 Sept 2026, 14:06 UTC190 viewsread 7 September 2026
Photo

🏒 Команда Андрея Разина начинает сезон с уверенной победы «Амур» не может обыграть «Металлург» уже пять матчей подряд. 🏒 PROХоккей

6 Sept 2026, 13:47 UTC178 viewsread 7 September 2026
Video

🔝 Толчинский — главный герой встречи в Магнитогорске Сергей набрал уже три очка в сегодняшнем матче. 🏒 PROХоккей

6 Sept 2026, 13:07 UTC184 viewsread 7 September 2026
Video

😈 «Амур» бросается в погоню! Кирилл Пилипенко забрасывает первую шайбу в дебютном матче за новую команду. 🏒 PROХоккей

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

Mentions

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

“PROХоккей | КХЛ NHL ТРАНСФЕРЫ” (@khokkeyi), 31,700 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/khokkeyi.

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.