На концерте раза три заканчивалась память, при том что я и не особо много снимала, пришлось кучу приложений поудалять там, а теперь заново все качать
custom 53618894807331062681

Channel
@voiiiid666
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
137subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002058583495 |
|---|---|
| Type | Channel |
| Username | @voiiiid666 |
| Created | Between 1 November 2023 and 31 May 2024— 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/voiiiid666 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 10:58 | 137 | -1 |
| 23 Aug 2026, 02:07 | 138 | -2 |
| 15 Aug 2026, 18:44 | 140 | -2 |
| 8 Aug 2026, 22:01 | 142 | no change |
| 7 Aug 2026, 17:37 | 142 | first reading |
15 posts held, back to 5 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 15 (5 August 2026 – 8 August 2026) |
| Views total | 1,279 |
| Reactions total | 177 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 22:01 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 2 videos 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.
177 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 44.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5361889480733106268 | 78 | 44.1% | |
| custom 5472148133104341827 | 24 | 13.6% | |
| custom 5407078742914782380 | 23 | 13.0% | |
| 💘 | 20 | 11.3% | |
| custom 5361591835204525833 | 17 | 9.60% | |
| 💅 | 12 | 6.78% | |
| 🦄 | 3 | 1.69% |
Custom emoji. 4 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 15 of the 15 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 177reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 5 August 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.
На концерте раза три заканчивалась память, при том что я и не особо много снимала, пришлось кучу приложений поудалять там, а теперь заново все качать
custom 53618894807331062681
Фоточки симпатичные
custom 536188948073310626810custom 54721481331043418271
Могу сказать что я на мгновение увидела дырку на жопе, хоть он попросил выключить свет, но не запечатлела, только мысленно
custom 53615918352045258332
Вот тут когда его на сцену поднимали он штаны порвал и потом в шорты переоделся
custom 53618894807331062687
Итог концерта: было круто, жарко, Руслан порвал очко
custom 536188948073310626812
Video message, posted without a caption
custom 536159183520452583312
Угадайте кто
custom 540707874291478238012
Еду на бал✌
custom 536188948073310626820custom 53615918352045258333
С другом забронили билеты на человека пука за две недели в каком-то пиздатом кинотеатре Как тебе такое колобок?
custom 536188948073310626812
Photo, posted without a caption
💅12custom 53618894807331062683🦄2
Ну какие бедолаги
custom 54721481331043418278
Как меня эти сказки заебали Тошнит от всего что снимается у нас в стране, полнейшее дерьмище
custom 547214813310434182715
Showing the 12 most recent of 15 posts we hold for @voiiiid666. 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.
“Пустота.” (@voiiiid666), 137 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/voiiiid666.
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.