Channel
@wafflerezka_slay777
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003950226554 |
|---|---|
| Type | Channel |
| Username | @wafflerezka_slay777 |
| Created | Between 1 April 2026 and 1 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/wafflerezka_slay777 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 12:31 | 3 | no change |
| 10 Aug 2026, 14:52 | 3 | first reading |
20 posts held, back to 1 August 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 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
✦me and who???✦ 1 вафлерезка 2 тапоок 3 Джуди хопс 4 блинкее 5 ачоятоо 6 sweetcom suka kak razhshfn спасибо хорошо 7 вафлерезка 2 8 роксинадзор 9 крутейшая ачоятоо 10 марчел6769 11 аниме тянка подушка кто
✦me and who???✦ привет закину в тупа мы 1 ачоятоо 2 вафлерезка бака цундере охаешечки даттебаешечки
Привет спасибо хорошо. По 2 занимать можна 1 вафлерезка 2 споук 3 ачоято 4 споук 5 блинкеек 6 блинке 7 споук 8 тапоок 9 свиткомм 10 добрi 11 споук
✦me and who???✦ привет тоже тупа мы кину 1 вафлерезка 2 аочятоо
✦me and who???✦ 1 ачоято Иван золо 2 вафлерезка
✦me and who???✦ 1 докс сват спортики 2 вафлерезка 3 аочято
Яикт 1 кивееееекс 2 вафлерезка
Яикто 1 тапокк 2 споук 3 ачоятоо 4 вафлерезка 5 блинкеек
Усе последнее в тупа мы 1 вафлерезка 2 блинкеекк
✦me and who???✦ 1 чипуха 2 вафлерезка
✦me and who???✦ 1 чипуха 2 вафлерезка
✦me and who???✦ усе последний 1 чипухаа 2 вафлерезка
Showing the 12 most recent of 20 posts we hold for @wafflerezka_slay777. 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“архивоо/резы” (@wafflerezka_slay777), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/wafflerezka_slay777.
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.