🔮🔮🔮
❤3🎃3custom 53412728216685500612

Channel
@lavka338
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
40subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003794876873 |
|---|---|
| Type | Channel |
| Username | @lavka338 |
| Created | Between 1 February 2026 and 16 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/lavka338 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 05:36 | 40 | +2 |
| 1 Sept 2026, 14:03 | 38 | -2 |
| 16 Aug 2026, 16:04 | 40 | +1 |
| 10 Aug 2026, 20:16 | 39 | no change |
| 9 Aug 2026, 02:30 | 39 | first reading |
11 posts held, back to 16 June 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 11 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
127 reactions across 9 posts, in 16 distinct kinds. The most used accounts for 17.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 22 | 17.3% | |
| custom 5341272821668550061 | 17 | 13.4% | |
| custom 5208712306799709998 | 15 | 11.8% | |
| custom 5226935857331592716 | 12 | 9.45% | |
| custom 5368334298204086360 | 11 | 8.66% | |
| custom 5363990222252038217 | 10 | 7.87% | |
| custom 5224336753577454560 | 8 | 6.30% | |
| custom 5456519601812700317 | 7 | 5.51% | |
| 💋 | 6 | 4.72% | |
| 🔥 | 6 | 4.72% | |
| ❤🔥 | 3 | 2.36% | |
| 🎃 | 3 | 2.36% | |
| custom 5242377055034701853 | 2 | 1.57% | |
| custom 5393263061484196883 | 2 | 1.57% | |
| 💘 | 2 | 1.57% | |
| custom 5240242451993629288 | 1 | 0.787% |
Custom emoji. 10 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 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 9 of the 11 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 127 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 16 June 2026 to 10 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.
🔮🔮🔮
❤3🎃3custom 53412728216685500612
Циррозность печени у кого то
💋6❤3❤🔥3custom 53639902222520382171
Wattäufer
❤6custom 52087123067997099985custom 54565196018127003175custom 52243367535774545601custom 52269358573315927161custom 53639902222520382171
Тигр
🔥6custom 53412728216685500613custom 53639902222520382173❤2
Некий спойлер в зин больше у меня ничего нет😀😀
❤8custom 53412728216685500613💘2
Никогда не буду сканить картинки
Чо вы тут чухните да
custom 52269358573315927167custom 52087123067997099985custom 53412728216685500614custom 52243367535774545601custom 53639902222520382171custom 53683342982040863601custom 54565196018127003171
Шо вы лысые
🌟🌟🌟🌟😢💅❔🌟😜
custom 53683342982040863609custom 52243367535774545605custom 52087123067997099984custom 52269358573315927161custom 53639902222520382171custom 53932630614841968831custom 54565196018127003171
Чекайте
custom 53412728216685500615custom 52269358573315927163custom 53639902222520382173custom 52087123067997099981custom 52243367535774545601custom 52402424519936292881custom 53683342982040863601custom 53932630614841968831
С божьей помощью оплатила премиум щас реакции вам чотенькие еще поставлю
custom 52423770550347018532
Showing the 11 most recent of 11 posts we hold for @lavka338. 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.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Bench🦇🧟” (@lavka338), 40 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/lavka338.
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.