Telegram RegisterThe public register of Telegram
Telegram profile photo for ХК «Сибирские Снайперы» ❄️ 🏒

Channel

ХК «Сибирские Снайперы» ❄️ 🏒

@hcsiberiansnipers

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry

21,613subscribers

-3 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001701016230
TypeChannel
Username@hcsiberiansnipers
DescriptionКоманда «Сибирские Снайперы» - часть хоккейного клуба «Сибирь». Играет в Молодежной хоккейной лиге. Домашние матчи команда проводит на «Сибирь-Арене».
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/hcsiberiansnipers

Topic

Sports — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 2 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hockeyclubsibir/2837331 Oct 2026, 04:59 UTC@hcsiberiansnipers/15694 · this entry31 Oct 2026, 05:06 UTC1.007 minutes
@hcsiberiansnipers/15770 · this entry3 Nov 2026, 14:22 UTC@hockeyclubsibir/285333 Nov 2026, 14:29 UTC1.008 minutes
@hcsiberiansnipers/15713 · this entry1 Nov 2026, 06:12 UTC@mhlrus/293872 Nov 2026, 07:41 UTC1.0025 hours
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
ChannelMatching postsText overlapTypical gapPublished first
@hockeyclubsibir12 (8/8 hand-verifiable sample passed)1.007 minuteseven
@mhlrus9 (8/8 hand-verifiable sample passed)1.008 minutes@mhlrus (6–3)

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 1 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 65 comparable posts for this entry, running 6 August 2026 to 15 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 @hcsiberiansnipers — which is this entry. That is a statement about our reading window, not a claim of authorship.

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

Growth

21,47121,67021,570.521,6136 August 202614 November 2026
67 measurements spanning 100 days, net -3. 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 21,441–21,700 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
14 Nov 2026, 05:0621,613-57
11 Nov 2026, 10:0521,670+30
9 Nov 2026, 12:4021,640+7
8 Nov 2026, 02:2821,633-18
7 Nov 2026, 00:2121,651-7
6 Nov 2026, 00:2521,658-4
5 Nov 2026, 03:2921,662+6
4 Nov 2026, 05:1121,656+22
3 Nov 2026, 07:2921,634-3
2 Nov 2026, 04:0021,637+6
1 Nov 2026, 04:3021,631+1
31 Oct 2026, 03:2921,630+54
30 Oct 2026, 00:1621,576-8
28 Oct 2026, 20:5021,584-7
27 Oct 2026, 17:3821,591-13
26 Oct 2026, 15:5121,604+6
25 Oct 2026, 16:0521,598+35
24 Oct 2026, 16:4421,563+29
23 Oct 2026, 18:1721,534-8
22 Oct 2026, 19:3721,542first reading

Engagement

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

ERR · 30 days
15.3%
avg views ÷ 21,613 subscribers
Avg views / post
3,300
99 posts measured
Reaction rate
3.79%
reactions ÷ views · ER floor
Posts in window
99
of 439 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 16 November 2026
Posts held439 (5 August 2026 – 16 November 2026)
Views total327,016
Reactions total12,392
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 03:51 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
≈6,580
Videos
≈3,730
Links
≈4,310

Lifetime counters from Telegram’s own channel header, read 16 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
1h 10m
Average length
35s

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

37,795 reactions across 419 posts, in 46 distinct kinds. The most used accounts for 58.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤21,91258.0%
❤‍🔥5,00413.2%
custom 54001910799558333743,6669.70%
💘1,8354.86%
😭1,0252.71%
🔥8062.13%
💔5191.37%
☃3720.984%
👀3030.802%
💋2350.622%
🍓2100.556%
custom 53392507811303568321630.431%
🎉1540.407%
⚡1490.394%
🗿1450.384%
😁1270.336%
🍾1220.323%
😱1210.32%
🥴1080.286%
👍1060.28%
26 further kinds7131.89%

Custom emoji. 2 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 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 439 of the 439 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 38,673 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

Telegram’s own ‘edited’ marker: 12 of 99 posts held from the last 30 days (12.1%) 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).

16 Nov 2026, 02:14 UTC≈4,380 views85 reactionsread 16 November 2026
Video

🏒 День игры! Сыграем с «Мамонтами Югры» ❄️ 🔠🔠 🦣 ⏰ 18:30 НСК 📍Новосибирск, «Сибирь-Арена» 📺 VK, YouTube, сайт и приложение МХЛ 🎫 Билеты Прицел на будущее 🎯

❤64❤‍🔥18💘3

15 Nov 2026, 10:00 UTC≈1,800 views170 reactionsread 16 November 2026
Forwarded from @hockeyclubsibirPhoto

Возвращение легенд! Михаил Абрамов и Даниил Валитов в составе, а вот Антон Косолапов приболел 🤒 А ещё и Ваня Рябов с нами! Открой в себе Сибирь ❄️

❤129❤‍🔥21custom 540019107995583337414👀2😁2🍓1💘1

15 Nov 2026, 10:00 UTC≈2,740 views87 reactionsread 16 November 2026

А кто это у нас тут под 73 номером?) 😉

❤68custom 540019107995583337414💘3🍓1😐1

15 Nov 2026, 07:37 UTC≈5,930 views190 reactionsread 16 November 2026

Posted without readable text

❤137☃23👏10custom 54001910799558333749❤‍🔥4💘4🍓1🔥1

14 Nov 2026, 09:08 UTC≈7,040 views162 reactionsread 16 November 2026
Video

Готовимся к охоте на «Мамонтов» 🦣 Прицел на будущее 🎯

❤116😁18🔥11custom 54001910799558333749❤‍🔥6👍1💘1

14 Nov 2026, 07:11 UTC≈8,350 views448 reactionsread 16 November 2026
Video

Эдуард Волков вернулся на пост главного тренера 👀 Прицел на будущее 🎯

❤292❤‍🔥75🎉50😨10💘6custom 54001910799558333746👍3😭3

13 Nov 2026, 06:31 UTC≈4,420 views393 reactionsread 16 November 2026
Video

Однажды «Снайпер», всегда «Снайпер»! 🤝 Удачи в карьере, Груня! ✊ Прицел на будущее 🎯

❤233💔85😭34💘16custom 540019107995583337411🤝8❤‍🔥4🍓1

12 Nov 2026, 10:54 UTC≈2,550 views295 reactionsread 16 November 2026
Forwarded from @hockeyclubsibirPhoto

Обмен со «Спартаком» Хоккейный клуб «Сибирь» совершил обмен с хоккейным клубом «Спартак», в результате которого нашу команду пополнил 32-летний нападающий Александр Гальченюк (12.02.1994, 185/88). В обратном направлении последовал защитник системы «Сибири» Александр Грунин. Также «Спартак» получил денежную компенсацию. Генеральный директор «Сибири» Лев Крутохвостов: - Обмен Грунина на Гальченюка – очень непростое …

😭242❤27😡9🥴5😨4💔3custom 54001910799558333742🍓1

12 Nov 2026, 09:55 UTC≈3,980 views138 reactionsread 16 November 2026
Photo

Лёд мы тоже не пропускаем ☝️ Прицел на будущее 🎯

❤91❤‍🔥19💘14custom 540019107995583337410😍2🍓1💋1

12 Nov 2026, 09:34 UTC≈3,840 views120 reactionsread 16 November 2026
Video

Тягаем железо, готовимся к играм, а как ваш день проходит? 🤨 Прицел на будущее 🎯

❤‍🔥55❤42custom 540019107995583337413💋6💘3🍓1

11 Nov 2026, 09:44 UTC≈4,150 views193 reactionsread 16 November 2026
Video

Отработаем! 💪 Прицел на будущее 🎯

❤‍🔥103❤53🏆16custom 540019107995583337415💘2🙈2☃1🍓1

10 Nov 2026, 14:38 UTC≈4,360 views176 reactionsread 16 November 2026
Forwarded from @mhlrusPhoto

Символическая сборная октября 🍁 Комментатор матчей и автор официального сайта Лиги Иван Костяев представляет символическую сборную, составленную из наиболее успешных игроков Лиги по итогам второго месяца OLIMPBET регулярного чемпионата МХЛ.

custom 5400191079955833374101❤60👀8❤‍🔥3💘3🍓1

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

@hcsiberiansnipers 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
10 August 2026
Most recent edit
22 August 2026

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 20 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.

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.

ХК «Сибирь»
@hockeyclubsibir · 89,999
#1
Команда 1962 | News HC Sibir
@team1962sibir · 13,252
#2
ТСЖ | ХК «Сибирь»
@hcsibir154 · 6,529
#3
КХЛ
@khl_official_telegram · 284,836
#4
ХК «Сибирь» сообщество фанатов
@sibirhockeyclub · 28,522
#5
Молодежная хоккейная лига I МХЛ
@mhlrus · 49,573
#6
Славься, Сибирь!
@sibirnovosib · 2,353
#7
Unknown Bogun / Неизвестный Богун
@siberian_hockey · 8,680
#8
Хозяева Сибири | HC SIBIR
@hcsibir2007 · 1,317
#9
Ерыкаловщина
@erykalov_s_shaiboi · 28,174
#10
Спортивная школа по хоккею «Сибирь» имени А.В. Тарасенко
@hockey_nso · 1,159
#11
Погудим
@pogudim · 1,037
#12
ФК «Сибирь»
@fcsib · 7,239
#13
Админ мира 🇷🇺🫡
@bigbob2015 · 213 (as read 23 September 2026)
#14
Трансферы КХЛ | ХОККЕЙ
@transfers_khl · 62,380
#15
хк сибирь 2011
@sibir2011 · 297
#16
Хоккейные Сливки
@hockey_slivki · 32,753
#17
Собачий диджей | Dj Huskydealer
@huskydelaer · 1,010
#18
ДРУЖИНА ❄️
@Druzhina_NSK · 2,018
#19
ХК «Красноярские Рыси»
@krsk_bobcats · 2,651
#20
ЧЕРКАС АТЛАНТ
@cherkasatlant · 49,563
#21
Снеговик ❄️
@HCsibi · 171
#22
Новосибирск с огоньком
@novosibtop · 61,120
#23
Роман с Хоккеем
@hockeywithroman · 57,982
#24
ХК «Авангард» Омск 🦅
@omskiyavangard · 332,958
#25
ВК «Локомотив-Новосибирск»
@lokovolleynsk · 32,387
#26
Atributika&Club
@atributikaclub · 25,786
#27
ХК Торпедо
@torpedonn · 60,984
#28
ЦЕНТР ЗИМНИХ ВИДОВ СПОРТА
@Dbe62JknbSRiNzY6 · 1,130
#29
Скользкий лёд
@skolzkyled · 46,300
#30
🔥Сочи.Огонь.🔥
@sochihc · 14,040
#31
ХК «Сибсельмаш»
@hcsibselmash · 2,509
#32
Мэтью на Мопеде 🛵
@matmoped · 170
#33
Мамонты Югры
@hc_mamonty_ugra · 2,196
#34
Матч! Хоккей
@hockey_match · 57,017
#35
Рыжебород из❄️Сибири❄️
@hockeyclubsibirservice · 11,001
#36
Любимый фотограф
@trufanovaphoto · 3,388
#37
АСТ-54 Black
@teleact54 · 268,197
#38
Hockeymans78
@Hockeymans78 · 23,909
#39
Трансферы МХЛ
@mhl_transfer · 8,583
#40
ХК «Омские Ястребы» | Официальный канал
@omsk_hawks · 16,218
#41
ГАУ НСО "Арена"
@sibirarena · 3,936
#42
АФИША НОВОСИБИРСК
@afishanovosibirsk · 39,818
#43
Климович Team ☕️🍃
@FanKlimovichTeam · 112
#44
Бедарев. Непрямой эфир
@bedarev_channel · 2,950
#45
Канал Алексея Шевченко, "День с Алексеем Шевченко"
@derzhiperedachu · 59,738
#46
Новосибирский паблик
@nskpub · 24,132
#47
Инцидент Новосибирск
@inc54 · 166,574
#48
НГС — новости Новосибирска
@ngs_news · 114,479
#49
Эй, Новосибирск!
@live_novosibirsk · 43,390
#50
АренаБреда
@arena_breda · 30,946
#51
Движение Первых | Новосибирская область
@mypervie54 · 4,696
#52
НОВОСТИ НОВОСИБИРСК
@mapnovosibirsk · 19,953
#53
Хоккейная правда
@coronahockey · 9,869
#54
ХК «Трактор» | Челябинск
@hctraktor · 104,700
#55
Хайруллин Live
@tebevukhokriknut · 40,349
#56
Новосибирский зоопарк
@nsk_zoo · 42,108
#57
дух, душа и тело
@miraclewrs · 2,678
#58
WHERETOGO Новосибирск
@wheretogonsk · 65,925
#59
Святой ЦЗВС😇
@kabanneeblan · 300
#60
Czvs channel
@czvschannel · 135
#61
Лилс✨
@ittsliil · 364
#62
BK6 | Богдан Конюшков
@konyushkov6 · 7,247
#63

Read from Telegram’s recommendation API, most recently 23 September 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.

ХК «Сибирь» сообщество фанатов
@sibirhockeyclub · 28,522
Telegram ranks this channel #1 of 69 here — alongside 68 others — read 8 September 2026
ХК «Сибирь»
@hockeyclubsibir · 89,999
Telegram ranks this channel #1 of 88 here — alongside 87 others — read 17 August 2026
Новосибирск с огоньком
@novosibtop · 61,120
Telegram ranks this channel #13 of 76 here — alongside 75 others — read 22 August 2026
Молодежная хоккейная лига I МХЛ
@mhlrus · 49,573
Telegram ranks this channel #14 of 99 here — alongside 98 others — read 25 August 2026
Новосибирский паблик
@nskpub · 24,132
Telegram ranks this channel #17 of 27 here — alongside 26 others — read 16 September 2026
Atributika&Club
@atributikaclub · 25,786
Telegram ranks this channel #18 of 96 here — alongside 95 others — read 12 September 2026
ВК «Локомотив-Новосибирск»
@lokovolleynsk · 32,387
Telegram ranks this channel #20 of 79 here — alongside 78 others — read 5 September 2026
Новосибирский зоопарк
@nsk_zoo · 42,108
Telegram ranks this channel #21 of 91 here — alongside 90 others — read 30 August 2026
Ерыкаловщина
@erykalov_s_shaiboi · 28,174
Telegram ranks this channel #27 of 94 here — alongside 93 others — read 10 September 2026
АСТ-54 Black
@teleact54 · 268,197
Telegram ranks this channel #35 of 71 here — alongside 70 others — read 10 August 2026
КХЛ
@khl_official_telegram · 284,836
Telegram ranks this channel #36 of 98 here — alongside 97 others — read 10 August 2026
Новости Новосибирска и Области
@topsmi54 · 42,285
Telegram ranks this channel #38 of 57 here — alongside 56 others — read 29 August 2026
Hockeymans78
@Hockeymans78 · 23,909
Telegram ranks this channel #45 of 90 here — alongside 89 others — read 15 September 2026
Эй, Новосибирск!
@live_novosibirsk · 43,390
Telegram ranks this channel #45 of 67 here — alongside 66 others — read 28 August 2026
Хоккейные Сливки
@hockey_slivki · 32,753
Telegram ranks this channel #46 of 96 here — alongside 95 others — read 4 September 2026
Новосибирск |Регион-54|
@region_nsk54 · 39,398
Telegram ranks this channel #50 of 60 here — alongside 59 others — read 30 August 2026
Инцидент Новосибирск
@inc54 · 166,574
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 12 August 2026
АФИША НОВОСИБИРСК
@afishanovosibirsk · 39,818
Telegram ranks this channel #55 of 84 here — alongside 83 others — read 30 August 2026
НОВОСТИ НОВОСИБИРСК
@mapnovosibirsk · 19,953
Telegram ranks this channel #57 of 80 here — alongside 79 others — read 27 September 2026
Om1: Новости Новосибирска и России
@Om1_nsk · 29,301
Telegram ranks this channel #57 of 85 here — alongside 84 others — read 6 September 2026
Типичный Новосибирск
@tipanovosib · 46,141
Telegram ranks this channel #57 of 77 here — alongside 76 others — read 27 August 2026
НГС — новости Новосибирска
@ngs_news · 114,479
Telegram ranks this channel #57 of 91 here — alongside 90 others — read 14 August 2026
Подслушано | Новосибирск и Область
@moynovosib · 28,327
Telegram ranks this channel #59 of 77 here — alongside 76 others — read 9 September 2026
ТикеБум.Новосибирск
@tboom_54 · 34,471
Telegram ranks this channel #60 of 75 here — alongside 74 others — read 3 September 2026

This channel appears in 28 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.

Q3739736 on Wikidata, read 15 November 2026
LabelSibirskie Snaypery
Descriptionjunior ice hockey team in Novosibirsk, Russia
Official sitehttps://snipers.hcsibir.ru/

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

“ХК «Сибирские Снайперы» ❄️ 🏒” (@hcsiberiansnipers), 21,613 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/hcsiberiansnipers.

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.