забила
custom 54699495994750597402

Channel
@emptyhll1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
23subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001559123411 |
|---|---|
| Type | Channel |
| Username | @emptyhll1 |
| Description | multi(millionaire) юз: @emptyhll |
| Created | 12 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/emptyhll1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 12:16 | 23 | no change |
| 7 Aug 2026, 19:50 | 23 | first reading |
17 posts held, back to 15 January 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 15 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 5 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.
31 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 58.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235453009407802974 | 18 | 58.1% | |
| custom 5469949599475059740 | 8 | 25.8% | |
| custom 5357214146838432227 | 5 | 16.1% |
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 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 16 of the 17 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 31reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 15 January 2026 to 15 May 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 54699495994750597402
Sticker, posted without a caption
custom 53572141468384322271
Photo, posted without a caption
custom 53572141468384322272
забыла
x_x
custom 52354530094078029742
ПОСЛЕ ДОЛГИХ ЗИМ ВСЕГДА ПРИХОДЕТ ЛЕТА 😁😁 ac me
custom 54699495994750597402
турист и босс итальянской мафии
custom 54699495994750597402
Sticker, posted without a caption
custom 54699495994750597402
😎😎😎 это тай деткоооо
custom 52354530094078029742
повседневность
custom 52354530094078029742
полуголая девушка набирает 10тисич лайков за час. . а сколько наберут эти макаки… ?
custom 52354530094078029742
всем qq + hi . я с моим худшим другом случайным образом попали в таиланд.. по этому завтра будет стрим ирл )
custom 52354530094078029742
Showing the 12 most recent of 17 posts we hold for @emptyhll1. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“хорни” (@emptyhll1), 23 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/emptyhll1.
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.