Posted without readable text
custom 53232868944972659566custom 54630567524906013006custom 54651638419711824125custom 54655740800674245563custom 51881612619505013942custom 52177358226352080611custom 52288073893308162151custom 54426490521749152191

Channel
@lizok_bounty
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
159subscribers
+0 since we began measuring on 2 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001808628246 |
|---|---|
| Type | Channel |
| Username | @lizok_bounty |
| Description | мой магнум опус инста: q_mymay |
| First recorded | 2 October 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lizok_bounty |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 16:22 | 159 | no change |
| 2 Oct 2026, 15:47 | 159 | first reading |
14 posts held, back to 9 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.
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 29 September 2026 |
|---|---|
| Posts held | 14 (9 September 2026 – 29 September 2026) |
| Views total | 2,687 |
| Reactions total | 262 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Oct 2026, 16:22 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.
Lifetime counters from Telegram’s own channel header, read 2 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
262 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 24.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463056752490601300 | 64 | 24.4% | |
| custom 5465574080067424556 | 53 | 20.2% | |
| custom 5323286894497265956 | 49 | 18.7% | |
| custom 5217735822635208061 | 35 | 13.4% | |
| custom 5228807389330816215 | 24 | 9.16% | |
| custom 5465163841971182412 | 15 | 5.73% | |
| custom 5188161261950501394 | 13 | 4.96% | |
| custom 5442649052174915219 | 9 | 3.44% |
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 14 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 262 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 9 September 2026 to 29 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.
Posted without readable text
custom 53232868944972659566custom 54630567524906013006custom 54651638419711824125custom 54655740800674245563custom 51881612619505013942custom 52177358226352080611custom 52288073893308162151custom 54426490521749152191
Posted without readable text
custom 54630567524906013005custom 53232868944972659564custom 52288073893308162152custom 51881612619505013941custom 52177358226352080611custom 54651638419711824121custom 54655740800674245561
Posted without readable text
custom 54655740800674245566custom 53232868944972659565custom 51881612619505013942custom 52177358226352080612custom 52288073893308162152custom 54630567524906013002custom 54651638419711824122
Posted without readable text
custom 54630567524906013008custom 52177358226352080616custom 53232868944972659563custom 54655740800674245563custom 51881612619505013941custom 52288073893308162151custom 54426490521749152191custom 54651638419711824121
Posted without readable text
custom 54630567524906013005custom 53232868944972659564custom 52177358226352080613custom 51881612619505013941custom 52288073893308162151custom 54651638419711824121custom 54655740800674245561
Спасибо 💙
custom 546305675249060130011custom 54655740800674245566custom 54426490521749152195custom 52288073893308162153
https://vk.ru/wall-1891628_12407 Поход первака САФУ 2026 — ВСЕ! вот как это было…
custom 52177358226352080615custom 54630567524906013003custom 54655740800674245563
Posted without readable text
custom 54630567524906013007custom 52288073893308162154custom 52177358226352080613custom 54655740800674245562
Posted without readable text
custom 54630567524906013005custom 52177358226352080614custom 53232868944972659564custom 54655740800674245562custom 51881612619505013941custom 52288073893308162151custom 54651638419711824121
на свидании с 10/10 🫶🏻
custom 54655740800674245565custom 54630567524906013003custom 52288073893308162152custom 51881612619505013941
вот такое ещё неформальное больше в походе меня не увидите 🥀
custom 53232868944972659569custom 52177358226352080617custom 54655740800674245566custom 51881612619505013941custom 52288073893308162151custom 54651638419711824121
я закрыла гештальт в службе безопасности 🫦
custom 546557408006742455611custom 53232868944972659563custom 51881612619505013942custom 54630567524906013002custom 52177358226352080611custom 52288073893308162151custom 54426490521749152191custom 54651638419711824121
Showing the 12 most recent of 14 posts we hold for @lizok_bounty. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“ЛИЗОК БАУНТИ” (@lizok_bounty), 159 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/lizok_bounty.
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.