Channel
@warmesswasser
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
210subscribers
+3 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002411231927 |
|---|---|
| Type | Channel |
| Username | @warmesswasser |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/warmesswasser |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 13:40 | 210 | +3 |
| 10 Sept 2026, 23:40 | 207 | +1 |
| 1 Sept 2026, 13:38 | 206 | +1 |
| 16 Aug 2026, 21:15 | 205 | -2 |
| 10 Aug 2026, 00:45 | 207 | no change |
| 10 Aug 2026, 00:17 | 207 | first reading |
12 posts held, back to 24 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 12 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
164 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 50.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5193083440500600588 | 83 | 50.6% | |
| custom 5233629228854953061 | 49 | 29.9% | |
| custom 5803190726082698724 | 32 | 19.5% |
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 11 of the 12 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 164 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 24 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.
у меня сегодня день рождения, можете репостнуть еще если хотите, можете закинуть на энергетик 2202208238143425
custom 523362922885495306119custom 51930834405006005885custom 58031907260826987244
с днем рождения меня
custom 519308344050060058812custom 52336292288549530614custom 58031907260826987244
охаешечки даттебаешечки
custom 580319072608269872412custom 51930834405006005883
я тут люблю сопли жевать
custom 51930834405006005886
тимофейский
custom 523362922885495306112custom 51930834405006005883custom 58031907260826987243
#sallyface #sallyfisher
custom 519308344050060058811custom 52336292288549530614custom 58031907260826987244
ну тут особо ничего криминального
custom 519308344050060058810custom 52336292288549530614
аватарки
custom 519308344050060058813custom 52336292288549530616custom 58031907260826987245
комментарии оставляйте сами
custom 51930834405006005889
Photo, posted without a caption
custom 51930834405006005881
File, posted without a caption
кстати вам были бы интересны такие портретики? если да, писаните в комменты, могу сделать
custom 519308344050060058810
Showing the 12 most recent of 12 posts we hold for @warmesswasser. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“тëплая вöда.” (@warmesswasser), 210 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/warmesswasser.
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.