Channel
@katarsau
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
519subscribers
+269 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003927464556 |
|---|---|
| Type | Channel |
| Username | @katarsau |
| Created | Between 1 April 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/katarsau |
Literature — 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 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 00:19 | 519 | +24 |
| 14 Sept 2026, 15:41 | 495 | +33 |
| 6 Sept 2026, 06:39 | 462 | +6 |
| 30 Aug 2026, 00:39 | 456 | +24 |
| 22 Aug 2026, 20:16 | 432 | +136 |
| 15 Aug 2026, 07:17 | 296 | +46 |
| 8 Aug 2026, 09:32 | 250 | no change |
| 8 Aug 2026, 06:06 | 250 | first reading |
8 posts held, back to 7 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 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 8 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
165 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 25.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5395605420683309185 | 42 | 25.5% | |
| custom 5242510564093081424 | 41 | 24.8% | |
| custom 5260558141224924677 | 34 | 20.6% | |
| custom 5190950954878399778 | 16 | 9.70% | |
| custom 5269716819681236448 | 12 | 7.27% | |
| custom 5192975258864346226 | 8 | 4.85% | |
| custom 5337289260976326754 | 8 | 4.85% | |
| custom 5377826193108142651 | 4 | 2.42% |
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 7 of the 8 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 165 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 7 August 2026 to 8 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.
🌟🌟 🌟🌟 five dates theory mini minsung au, где Минхо, пытаясь затянуть раны от прошлых отношений, по глупости соглашается на пять слепых свиданий. первые четыре оказываются настолько провальными, что последнее кажется пыткой, которую хочется скорее пройти забыть. вот только Джисон, оказавшийся не в то время и не в том месте, совсем не понимает, кто такой Минхо и что он хочет. 🩹 #bodyelse
Signed ﹫
p. 87. бар { #Zeitnot }
custom 526055814122492467724custom 53956054206833091858custom 51909509548783997787custom 51929752588643462261
Signed katarsis.
кто хочет вместо меня написать главу
custom 52425105640930814249custom 53956054206833091852
Signed katarsis.
p. 86. хочется лечь на асфальт { #Zeitnot }
custom 539560542068330918532custom 52425105640930814249custom 52697168196812364489custom 53372892609763267543custom 53778261931081426512
Signed katarsis.
p. 85. заебались все { #Zeitnot }
custom 524251056409308142423custom 51929752588643462267custom 52605581412249246776custom 52697168196812364483custom 53372892609763267542custom 53778261931081426512
Signed katarsis.
𝒶𝑔𝒶𝒾𝓃 𝒶𝓃𝒹 𝒶𝑔𝒶𝒾𝓃 𝓶𝓲𝓷𝓼𝓾𝓷𝓰 𝓪𝓾 жизнь течёт размеренно и одинаково, пока кто-то случайно не появляется в ней и не ломает её. или чинит? #aanda
custom 53372892609763267543
Signed ﹫
как вам новый альбом?? уже слушали? какая песня понравилась больше всего?
custom 51909509548783997789
Signed katarsis.
~ 🔤eel 🔤he 🔤drenaline — Ау, где Хенджин живет скоростью своего байка и пьет двойной эспрессо, запивая его ледяной водой — заглушает кофеин, — а Сынмин, как оказывается, когда Хенджин впервые заходит в кафе, где он работает, готовит это эспрессо лучше всех. Но на пике своей усталости Сынмин принесет совсем не то, что нужно Хенджину... А Чан и Минхо — друзья этих двоих, которые молча (иногда нет) наблюдают, но завора…
custom 52605581412249246774
Signed ﹫
Showing the 8 most recent of 8 posts we hold for @katarsau. 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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“under the ice” (@katarsau), 519 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/katarsau.
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.