Channel
@sankxxsu
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
518subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002302572033 |
|---|---|
| Type | Channel |
| Username | @sankxxsu |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/sankxxsu |
Music — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 14:02 | 518 | -3 |
| 3 Sept 2026, 17:00 | 521 | +1 |
| 27 Aug 2026, 19:14 | 520 | -6 |
| 21 Aug 2026, 03:14 | 526 | -2 |
| 14 Aug 2026, 14:55 | 528 | +4 |
| 6 Aug 2026, 18:32 | 524 | no change |
| 6 Aug 2026, 05:32 | 524 | first reading |
14 posts held, back to 23 July 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 1 page 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 14 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
643 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 32.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5240185724065565096 | 208 | 32.3% | |
| custom 5267125511292735038 | 204 | 31.7% | |
| custom 5307996673484542686 | 193 | 30.0% | |
| custom 5429202815241173135 | 38 | 5.91% |
Custom emoji. Every 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 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 14 of the 14 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 643 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 23 July 2026 to 3 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.
К лайнапу присоединяется angelgrind❕ последние билеты первой волны тут👈
custom 54292028152411731355custom 52401857240655650962custom 52671255112927350382
Signed чисто случайно
я люблю гришу ангелгринда
custom 542920281524117313513custom 52401857240655650969custom 52671255112927350389
Signed чисто случайно
нахайпили арине на руке.
custom 524018572406556509610custom 52671255112927350388custom 54292028152411731356
Signed чисто случайно
на тату только к ней ❤️ спб/мск
custom 52671255112927350387custom 52401857240655650963custom 54292028152411731353
Signed чисто случайно
Люблю Их 😅
custom 526712551129273503817custom 524018572406556509611custom 542920281524117313511
Signed чисто случайно
по вопросам рек и вп - @sanketsume
custom 524018572406556509629custom 530799667348454268611custom 526712551129273503810
Signed sanketsu
Video message, posted without a caption
custom 524018572406556509631custom 530799667348454268616custom 526712551129273503814
Signed sanketsu
Video message, posted without a caption
custom 524018572406556509626custom 526712551129273503815custom 530799667348454268612
Signed sanketsu
Video message, posted without a caption
custom 530799667348454268621custom 524018572406556509614custom 526712551129273503813
Signed sanketsu
выбила хачиваре из лутбокса по чикаве
custom 530799667348454268630custom 526712551129273503817custom 524018572406556509611
Signed sanketsu
File, posted without a caption
custom 530799667348454268631custom 526712551129273503816custom 524018572406556509612
Signed sanketsu
❤️
custom 530799667348454268644custom 524018572406556509620custom 526712551129273503817
Signed sanketsu
Showing the 12 most recent of 14 posts we hold for @sankxxsu. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“санкетсу” (@sankxxsu), 518 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/sankxxsu.
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.