Channel
@y00u_dreams
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
71subscribers
+40 since we began measuring on 25 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002909786194 |
|---|---|
| Type | Channel |
| Username | @y00u_dreams |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/y00u_dreams |
Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 87% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 11:26 | 71 | -3 |
| 28 Oct 2026, 05:18 | 74 | -6 |
| 20 Oct 2026, 08:37 | 80 | -1 |
| 12 Oct 2026, 21:09 | 81 | +48 |
| 3 Oct 2026, 01:56 | 33 | +2 |
| 25 Sept 2026, 03:22 | 31 | first reading |
20 posts held, back to 5 September 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 20 posts for this entry, the most recent from 25 September 2026. An engagement rate over an empty window would be a number about nothing.
64 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 23.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5426970871061309365 | 15 | 23.4% | |
| custom 5240100503324499878 | 12 | 18.8% | |
| custom 5307769448239765027 | 11 | 17.2% | |
| custom 5326049503361397544 | 11 | 17.2% | |
| custom 5278369288997084153 | 9 | 14.1% | |
| custom 5402156852127495947 | 6 | 9.38% |
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 14 of the 20 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 64 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 September 2026 to 25 September 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.
⎯⎯🔡озыгрыш ! ! ㅤㅤㅤㅤㅤㅤот м𝘂н𝗮к𝗼 п𝗽𝘂зы : 1 место — 💍 / 💎 / 🏆 2 - 3 места — 🎂 / 💐 / 🚀 4 - 5 места — 🎁 / 🌹 𝘆𝗰л𝗼вия для 𝘆ч𝗮стия : 1 . подписка без дальнейшей отписки . отписка — бан и запрет на участие в следующих розыгрышах . 2 . рт в свое инфо не стикером и не гиф . 3 . доки + юз + порядковый номер в коммы . ♡゙ㅤитоги на 30 участников ( подумаю еще . . )
Бля ну мы 🥹💋
custom 52401005033244998782custom 54021568521274959472custom 53077694482397650271
Posted without readable text
custom 54021568521274959471
Sticker, posted without a caption
custom 54269708710613093652
Sticker, posted without a caption
custom 53260495033613975442custom 53077694482397650271custom 54269708710613093651
Актива сорян что нет я заебался в последнее время проблемы решать да и учёба мозги ебёт 😬 Инфо в рест уйдёт пока всё плюс минус не решится
custom 54269708710613093652custom 53077694482397650271custom 53260495033613975441
🔸🅰🅰🅰🅰🅰🅰🅰🅰🔸 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 17.09.26-24.09.26 • УСЛОВИЯ • 1. Быть обязательно подписанным на меня ← 2. Переслать данный пост к себе в активный канал/группу 3. Скинуть в комментарии под этот пост пруфы (пункт 2) 4. Тыкнуть кнопочку ниже!! 🆎🅰🅰🅰🅰 будет 4 места, а именно : 🔸Первое место: Полноценный арт + чиби арт 🔸Второе место: Полноценный арт 🔸Третье место: Чиби арт 🔸Четвёртое место: Менее проработанный чиби а…
custom 52401005033244998782custom 54269708710613093652
17.09.2026! В этот прекрасный день Гумер и ДВлопер вступили в брак!🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 Репост если им суждено здохнуть 🤩🤩
custom 53077694482397650274custom 52783692889970841531custom 53260495033613975441
Всё в архив закинул 😀😀
custom 54269708710613093654
Sticker, posted without a caption
custom 54269708710613093651
File, posted without a caption
custom 54269708710613093652custom 53077694482397650271custom 53260495033613975441
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @y00u_dreams. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“(Рест) ⌦◛ˎ✧𝚄𝚗fo Goomer ✱ˊ◠ 🥧” (@y00u_dreams), 71 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/y00u_dreams.
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.