Telegram RegisterThe public register of Telegram
Telegram profile photo for NBSK HOCKEY TEAM

Channel

NBSK HOCKEY TEAM

@nbsk_team

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

6,367subscribers

-62 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001397224822
TypeChannel
Username@nbsk_team
Created7 September 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/nbsk_team

Growth

6,3646,4296,396.57 August 2026 — 6,429 subscribers7 August 2026 — 6,429 subscribers8 August 2026 — 6,427 subscribers11 August 2026 — 6,407 subscribers14 August 2026 — 6,401 subscribers18 August 2026 — 6,396 subscribers21 August 2026 — 6,382 subscribers24 August 2026 — 6,380 subscribers27 August 2026 — 6,376 subscribers30 August 2026 — 6,375 subscribers1 September 2026 — 6,364 subscribers5 September 2026 — 6,367 subscribers6,3677 August 20265 September 2026
12 measurements spanning 29 days, net -62. 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 6,354–6,439 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 17:006,367+3
1 Sept 2026, 20:266,364-11
30 Aug 2026, 03:576,375-1
27 Aug 2026, 10:026,376-4
24 Aug 2026, 19:156,380-2
21 Aug 2026, 12:056,382-14
18 Aug 2026, 01:126,396-5
14 Aug 2026, 19:466,401-6
11 Aug 2026, 04:316,407-20
8 Aug 2026, 01:126,427-2
7 Aug 2026, 09:156,429no change
7 Aug 2026, 09:046,429first reading

Engagement

24 posts held, back to 25 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 24 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
45s
Average length
9s

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

493 reactions across 24 posts, in 12 distinct kinds. The most used accounts for 45.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
22445.4%
🔥10922.1%
👍5210.5%
😱326.49%
❤‍🔥234.67%
🍾204.06%
🎉183.65%
💘91.83%
🏆20.406%
🤝20.406%
🕊10.203%
😍10.203%

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

Measured over the 24 most recent posts we hold, published 25 May 2026 to 10 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

10 Aug 2026, 10:22 UTC395 views15 reactionsread 12 August 2026
Photo

Уже восьмой год подряд Подмосковье на некоторое превращается в настоящую хоккейную столицу - здесь встречаются команды, болельщики и те, кто просто любит хоккей ❤️👍 🌨️ OviCup - это больше, чем турнир. Это настоящий хоккейный праздник! До встречи в следующем году! 🏒

🔥11❤‍🔥3🏆1

8 Aug 2026, 15:14 UTC522 views15 reactionsread 12 August 2026
Video

🏆 Вот и завершился OviCup! Было много яркого хоккея, эмоций, красивых голов и настоящей борьбы, а уже сегодня узнали победителя VIII Кубка Александра Овечкина. 🔴⚪️ «Спартак» — обладатель главного трофея турнира! Поздравляем команду с заслуженной победой и благодарим всех участников за этот невероятный хоккейный праздник! 🏒❤️

11🔥3❤‍🔥1

8 Aug 2026, 10:43 UTC486 views15 reactionsread 12 August 2026
Photo

✨Матч звёзд завершился! Он получился именно таким, каким и должен быть: громким, зрелищным, богатым на голы! Случился настоящий праздник хоккея ⚡️🥅 Матч завершился со счётом 🏒🏒🏒, победила дружба!

9🔥4👍2

8 Aug 2026, 10:23 UTC348 views13 reactionsread 10 August 2026
Video message

Video message, posted without a caption

6🔥5👍2

8 Aug 2026, 10:18 UTC337 views12 reactionsread 10 August 2026
Video message

Video message, posted without a caption

6🔥4👍2

8 Aug 2026, 10:17 UTC348 views9 reactionsread 10 August 2026
Video message

Video message, posted without a caption

🔥52👍2

8 Aug 2026, 09:47 UTC363 views12 reactionsread 10 August 2026
Video message

Video message, posted without a caption

5🔥5👍2

8 Aug 2026, 09:32 UTC339 views27 reactionsread 10 August 2026
Photo

Матч Звёзд стартанул! За какую команду болеете? ♥️ - team Овечкина 🔥 - team Ковальчука

22🔥4🏆1

8 Aug 2026, 09:17 UTC141 views7 reactionsread 8 August 2026
Video message

Video message, posted without a caption

5👍1🔥1

8 Aug 2026, 09:14 UTC159 views7 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥51👍1

8 Aug 2026, 09:11 UTC121 views7 reactionsread 8 August 2026
Photo

Мытищи сегодня очень громкие! 🎧 Кто прямо сейчас находится на арене? Перекличка в комментах!

5👍1🔥1

8 Aug 2026, 08:52 UTC163 views9 reactionsread 8 August 2026
Video message

Video message, posted without a caption

5👍2🔥2

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

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

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.

ХОККЕЙ ЗБС 🏒
@hockeyzbz · 52,564
Telegram ranks this channel #52 of 88 here — alongside 87 others — read 24 August 2026
ЧЕРКАС АТЛАНТ
@cherkasatlant · 50,470
Telegram ranks this channel #61 of 95 here — alongside 94 others — read 25 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“NBSK HOCKEY TEAM” (@nbsk_team), 6,367 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/nbsk_team.

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.