Channel
@sskremlizzss
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
218subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001674231693 |
|---|---|
| Type | Channel |
| Username | @sskremlizzss |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/sskremlizzss |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 04:18 | 218 | +1 |
| 8 Aug 2026, 10:46 | 217 | no change |
| 7 Aug 2026, 17:10 | 217 | first reading |
6 posts held, back to 1 May 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 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 6 posts for this entry, the most recent from 25 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
188 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5334794078250882782 | 45 | 23.9% | |
| custom 5469681185493897688 | 44 | 23.4% | |
| custom 5237884295904775016 | 39 | 20.7% | |
| custom 5359594456368574441 | 37 | 19.7% | |
| custom 5359608427897194112 | 16 | 8.51% | |
| custom 5427106793891319923 | 7 | 3.72% |
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 areTelegram’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 6 of the 6 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 188reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 1 May 2026 to 25 June 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.
вот и всё… Неплохая получилась история :)
custom 533479407825088278212custom 52378842959047750167custom 54696811854938976886custom 53595944563685744412custom 53596084278971941121custom 54271067938913199231
Signed sskremlizz
сдали госы 🌟🙏
custom 535959445636857444115custom 54696811854938976889custom 52378842959047750167custom 53347940782508827823custom 53596084278971941122
Signed sskremlizz
☝️☝️☝️
custom 54696811854938976887custom 53347940782508827825custom 52378842959047750164custom 53595944563685744412custom 53596084278971941122custom 54271067938913199231
Signed sskremlizz
и я туда же
custom 533479407825088278213custom 52378842959047750169custom 53596084278971941128custom 53595944563685744414custom 54696811854938976883custom 54271067938913199231
Signed sskremlizz
ойойой черт возьми как же я вайбую
custom 53347940782508827829custom 54696811854938976886custom 53595944563685744414custom 54271067938913199234custom 52378842959047750162custom 53596084278971941122
Signed sskremlizz
💥💥💥
custom 546968118549389768813custom 523788429590477501610custom 535959445636857444110custom 53347940782508827823custom 53596084278971941121
Signed sskremlizz
Showing the 6 most recent of 6 posts we hold for @sskremlizzss. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“ssкрéмлизз” (@sskremlizzss), 218 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/sskremlizzss.
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.