Telegram RegisterThe public register of Telegram

Channel

SNT (Sentinels)

@SNT_sentinels

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

971subscribers

-6 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003835035581
TypeChannel
Username@SNT_sentinels
CreatedBetween 1 February 2026 and 18 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/SNT_sentinels

Growth

9719779748 Aug 2026, 06:03 — 977 subscribers8 Aug 2026, 18:37 — 971 subscribers8 Aug 2026, 06:038 Aug 2026, 18:37
2 measurements taken within a single day, net -6. 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 970–978 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 18:37971-6
8 Aug 2026, 06:03977first reading

Engagement

19 posts held, back to 18 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 19 posts for this entry, the most recent from 6 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

69 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3347.8%
👍1623.2%
custom 53236226578605772621318.8%
👌710.1%

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

Measured over the 19 most recent posts we hold, published 18 April 2026 to 6 May 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

6 May 2026, 16:24 UTC831 views5 reactionsread 8 August 2026

🚀 SNT_Standoff 2 FastCup официально подошёл к концу, несмотря на кучу технических поражений и прочих проблем, определились призеры и команда победитель! ✅Итоги турнира 1. Qadam 2. Hltvy 3. The Legengs Благодарим команды за участие, надеемся, что технических проблем и поражений будет становиться меньше.

3👌1👍1

3 May 2026, 17:34 UTC793 viewsread 8 August 2026
Photo

SN - Hltvy Победа хлтв ✅ ФИНАЛ: Hltvy - Qadam 21:00 мск Бо3

3 May 2026, 16:34 UTC764 viewsread 8 August 2026

❌ команда 1337 Техническое поражение

3 May 2026, 16:01 UTC790 views2 reactionsread 8 August 2026

SN тех.поражение - неявка на игру. Полуфиналы! 1/2 финала Qadam - 1337 19:30 мск Hltvy - The Legengs 20:30 мск

2

3 May 2026, 14:42 UTC742 views4 reactionsread 8 August 2026

❌White Gun Исключение с турнира, отказ играть на регионе Польша Qadam в 1/2 1337 в 1/2 The Legengs в 1/2 Ждите ещё полуфиналиста между парой Sn и HLTV

4

3 May 2026, 14:40 UTC694 views3 reactionsread 8 August 2026
Photo

Sentinels - The Legengs Победа легенд✅

3

3 May 2026, 13:15 UTC669 views3 reactionsread 8 August 2026

команда Spokoynich тех.поражение.

👍21

3 May 2026, 12:51 UTC687 viewsread 8 August 2026

Команды 1337 и Spokoynich через 10 минут игра, кэпы в лобби жду пикать карты.

2 May 2026, 18:08 UTC676 views2 reactionsread 8 August 2026
Photo

❗️ Внимание, изменения в расписании для команд Hltvy, SN, Qadam и White Gun Остальных команд не касается!

1👍1

2 May 2026, 17:50 UTC637 viewsread 8 August 2026
Photo

Актуальная сетка! ❗️Время: начало 3 мая 16:00 МСК Регион игры: Польша

2 May 2026, 16:59 UTC668 views7 reactionsread 8 August 2026
Photo

Не выкладывали сетку только потому что человек пишет в заявке своей команды: МНЕ ЛЕНЬ ИСКАТЬ АЙДИ ИГРОКА, простите, а кто там будет каждый раз играть? Ребят, из-за подобного отношения и затягивается турнир, отсутствует сетка, и вам приходится очень долго ждать! Будет другая команда вместо них, придется перенести турнир на завтра.

7

2 May 2026, 11:27 UTC660 viewsread 8 August 2026

У нас 7 команд на турнире, нужна ещё одна чтобы начать делать сетку.

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

Citation-graph rank

Citation-graph rank — 246,910 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“SNT (Sentinels)” (@SNT_sentinels), 971 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/SNT_sentinels.

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.