Channel
@ultrasleepywitch
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
475subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001627489000 |
|---|---|
| Type | Channel |
| Username | @ultrasleepywitch |
| 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 | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 13 September 2026 |
| On Telegram | t.me/ultrasleepywitch |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 5 Sept 2026, 05:39 | 475 | +1 |
| 22 Aug 2026, 16:48 | 474 | +1 |
| 15 Aug 2026, 18:12 | 473 | -2 |
| 9 Aug 2026, 00:55 | 475 | -1 |
| 8 Aug 2026, 20:45 | 476 | first reading |
12 posts held, back to 27 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
109 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 25.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5267035420058729664 | 28 | 25.7% | |
| custom 5442741935137636649 | 25 | 22.9% | |
| custom 5328027829722431396 | 21 | 19.3% | |
| custom 5194951162863829437 | 16 | 14.7% | |
| custom 5357324501728113160 | 12 | 11.0% | |
| custom 5438651232191268558 | 4 | 3.67% | |
| custom 5195446089125216027 | 3 | 2.75% |
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 12 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 109 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 27 July 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.
почему нет хат на восстания за 30к 50 квадратов на пятом этаже с лифтом с кози дофамин питерест интерьером, сушильной и посудомоечной машинами, ванной и столом для пула?
custom 532802782972243139610custom 53573245017281131603custom 54427419351376366493
ну детокс у меня и чо блядь
custom 544274193513763664914custom 53280278297224313963custom 51949511628638294371custom 52670354200587296641custom 53573245017281131601
Photo, posted without a caption
custom 51949511628638294378custom 54427419351376366496custom 52670354200587296644
Video message, posted without a caption
custom 53573245017281131605custom 54386512321912685581
Video message, posted without a caption
custom 52670354200587296642
Video message, posted without a caption
custom 51954460891252160272
Video message, posted without a caption
custom 51949511628638294374custom 52670354200587296642
выдался какой то детокс, еду в спб. в лс отвечу только близким!!! сейчас мне реально ОХУЕННО
custom 53280278297224313966
сегодня на жутко сексуальном https://music.yandex.ru/album/4979308/track/28036283?ref_id=465ED5E5-1CA4-4A41-B4BD-61F2275DEA56&utm_medium=copy_link
custom 51954460891252160271custom 54386512321912685581custom 54427419351376366491
6️⃣7️⃣
custom 52670354200587296642custom 51949511628638294371custom 53573245017281131601custom 54386512321912685581
СУЧКА СЕГОДНЯ СИКСЕВАН РЕБЯТА 67WWWWWW67
custom 52670354200587296643custom 51949511628638294372custom 54427419351376366491
все эти факбои хотят быть мной, но держат это в секрете йоу https://music.yandex.ru/album/39947139/track/146647834?ref_id=8347D664-8D16-44E8-A43E-46D7535B91BD&utm_medium=copy_link
custom 526703542005872966414custom 53280278297224313962custom 53573245017281131602custom 54386512321912685581
Showing the 12 most recent of 12 posts we hold for @ultrasleepywitch. 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 4 registered channels — 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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“клуб любителей сыра” (@ultrasleepywitch), 475 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/ultrasleepywitch.
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.