Channel
@kssseshi
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
170subscribers
+1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002373276839 |
|---|---|
| Type | Channel |
| Username | @kssseshi |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 28 September 2026 |
| On Telegram | t.me/kssseshi |
Other / unclassifiable — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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 |
|---|---|---|
| 14 Sept 2026, 03:01 | 170 | +1 |
| 6 Sept 2026, 05:02 | 169 | -2 |
| 20 Aug 2026, 15:26 | 171 | +1 |
| 13 Aug 2026, 07:37 | 170 | +1 |
| 12 Aug 2026, 14:16 | 169 | first reading |
18 posts held, back to 1 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 18 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
208 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 51.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5424701530601183180 | 108 | 51.9% | |
| custom 5427078919553568458 | 35 | 16.8% | |
| custom 5424897789131774474 | 26 | 12.5% | |
| custom 5424947348759400919 | 11 | 5.29% | |
| custom 5424623010009076047 | 10 | 4.81% | |
| custom 5424850114994786822 | 10 | 4.81% | |
| custom 5425118709364581603 | 6 | 2.88% | |
| custom 5424853606803197083 | 2 | 0.962% |
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 17 of the 18 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 208 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 1 July 2026 to 9 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.
ловите вайб осени??? и я не очень пока не нашла места этому "catwar autumn" дурацкому, все равно скорее всего удлинять придется в коммы закину прошлые дизы
custom 54247015306011831806custom 54248977891317744746custom 54248501149947868223custom 54246230100090760472
🤫🤫🤫
custom 54247015306011831809custom 54270789195535684582
не буду заканчивать покажу что есть появилась идея на дизайн осени спасибо полухутенко но реализация очень хромает ничего не обещаю 🙌
custom 542707891955356845812custom 54246230100090760474
ну и ладно согласна донатить в эту помойку отстой 👎👎
custom 54246230100090760474custom 54248977891317744743
порисую за сундуки поддержки о колве договоримся пиши 123 👇
custom 54247015306011831805
во рабочее прикольные штуки вдохновленные крутым тату мастером оставила его юз в тт посмотрите обязательно у него очень крутецкие работы и головастик-стив
custom 54247015306011831805custom 54248977891317744745
атакам привет остальным ну вы поняли делюсь ючиком впереди еще один ии ээм референс стива вроде планируется
custom 542470153060118318014custom 54248536068031970832
але да ну как там с атаками
custom 542707891955356845813
"С каким блоком ассоциируется ваш персонаж?" ну он тыковка наверное я не знаю?? а вообще может земля Стив все таки
custom 542470153060118318013custom 54248977891317744743
атаки будут но не сегодня 👋 и не завтра
custom 54251187093645816036custom 54248501149947868222custom 54248977891317744742
рисовала сервала а вышла какая-то гиена?? 😓 4 атака
custom 542470153060118318022
попала?🔫 3 атака снова оливка мне нравится этот волосатый малышок те самые новые кисти но чес не очень зашли
custom 542470153060118318015
Showing the 12 most recent of 18 posts we hold for @kssseshi. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“kssseshi” (@kssseshi), 170 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/kssseshi.
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.