Channel
@whmss
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
262subscribers
+15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002495761041 |
|---|---|
| Type | Channel |
| Username | @whmss |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/whmss |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 12:03 | 262 | +3 |
| 23 Aug 2026, 06:15 | 259 | +6 |
| 15 Aug 2026, 01:06 | 253 | +6 |
| 8 Aug 2026, 09:34 | 247 | no change |
| 7 Aug 2026, 19:43 | 247 | first reading |
6 posts held, back to 22 June 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 20 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
200 reactions across 5 posts, in 10 distinct kinds. The most used accounts for 21.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226693170204542265 | 43 | 21.5% | |
| 👀 | 28 | 14.0% | |
| custom 5399852868461170388 | 26 | 13.0% | |
| 🕊 | 25 | 12.5% | |
| custom 5436147072984183126 | 23 | 11.5% | |
| custom 5330200627907681085 | 21 | 10.5% | |
| 👻 | 14 | 7.00% | |
| custom 5384106178324215504 | 13 | 6.50% | |
| custom 5393178712621481867 | 6 | 3.00% | |
| custom 5325712322658854095 | 1 | 0.5% |
Custom emoji. 7 of the rows above are 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 5 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 200reactions 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 22 June 2026 to 20 July 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.
zdravstvuyte🤩
custom 533020062790768108516custom 539985286846117038812custom 522669317020454226511custom 53931787126214818673custom 53257123226588540951custom 53841061783242155041custom 54361470729841831261
🕊️🕊️
давай не дадим им повод, без мести и боли..
🕊14custom 539985286846117038812custom 54361470729841831262
лень посты выкладывать, пересматривайте старые😉
custom 538410617832421550412👀11custom 543614707298418312611custom 52266931702045422657custom 53302006279076810854
what remains of edith finch ужасная игра. это конец моей личности но я вам советую!
🕊7👀5custom 52266931702045422655custom 53931787126214818673custom 54361470729841831263
помойка
custom 522669317020454226520👻14👀12custom 54361470729841831266🕊4custom 53998528684611703882custom 53302006279076810851
Showing the 6 most recent of 6 posts we hold for @whmss. 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“pathetic:(” (@whmss), 262 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/whmss.
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.