Telegram RegisterThe public register of Telegram

Channel

Bench🦇🧟

@lavka338

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

39subscribers

+0 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003794876873
TypeChannel
Username@lavka338
DescriptionМазги ыыыэуэээыаауувээаээ
CreatedBetween 1 February 2026 and 16 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/lavka338

Growth

399 August 2026 — 39 subscribers10 August 2026 — 39 subscribers9 August 202610 August 2026
2 measurements spanning 2 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 38–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 20:1639no change
9 Aug 2026, 02:3039first reading

Engagement

11 posts held, back to 16 June 2026the 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 · 30 days
78.5%
avg views ÷ 39 subscribers
Avg views / post
30.6
5 posts measured
Reaction rate
43.8%
reactions ÷ views · ER floor
Posts in window
5
of 11 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held11 (16 June 202610 August 2026)
Views total153
Reactions total67
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 20:16 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.

What this channel posts

Photos
75
Videos
3
Links
1

Lifetime counters from Telegram’s own channel header, read 10 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.

Reaction mix

127 reactions across 9 posts, in 16 distinct kinds. The most used accounts for 17.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2217.3%
custom 53412728216685500611713.4%
custom 52087123067997099981511.8%
custom 5226935857331592716129.45%
custom 5368334298204086360118.66%
custom 5363990222252038217107.87%
custom 522433675357745456086.30%
custom 545651960181270031775.51%
💋64.72%
🔥64.72%
❤‍🔥32.36%
🎃32.36%
custom 524237705503470185321.57%
custom 539326306148419688321.57%
💘21.57%
custom 524024245199362928810.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 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 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 127reactions 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.

Recent posts

10 Aug 2026, 18:22 UTC11 views8 reactionsread 10 August 2026
Photo

🔮🔮🔮

3🎃3custom 53412728216685500612

9 Aug 2026, 13:27 UTC18 views13 reactionsread 10 August 2026
Photo

Циррозность печени у кого то

💋63❤‍🔥3custom 53639902222520382171

8 Aug 2026, 17:38 UTC21 views19 reactionsread 10 August 2026
Photo

Wattäufer

6custom 52087123067997099985custom 54565196018127003175custom 52243367535774545601custom 52269358573315927161custom 53639902222520382171

1 Aug 2026, 11:02 UTC42 views14 reactionsread 10 August 2026
Photo

Тигр

🔥6custom 53412728216685500613custom 536399022225203821732

27 Jul 2026, 11:34 UTC61 views13 reactionsread 10 August 2026
Photo

Некий спойлер в зин больше у меня ничего нет😀😀

8custom 53412728216685500613💘2

27 Jun 2026, 21:47 UTC75 views20 reactionsread 10 August 2026
Photo

Чо вы тут чухните да

custom 52269358573315927167custom 52087123067997099985custom 53412728216685500614custom 52243367535774545601custom 53639902222520382171custom 53683342982040863601custom 54565196018127003171

24 Jun 2026, 17:06 UTC85 views22 reactionsread 10 August 2026
Photo

🌟🌟🌟🌟😢💅❔🌟😜

custom 53683342982040863609custom 52243367535774545605custom 52087123067997099984custom 52269358573315927161custom 53639902222520382171custom 53932630614841968831custom 54565196018127003171

16 Jun 2026, 16:51 UTC95 views16 reactionsread 10 August 2026

Чекайте

custom 53412728216685500615custom 52269358573315927163custom 53639902222520382173custom 52087123067997099981custom 52243367535774545601custom 52402424519936292881custom 53683342982040863601custom 53932630614841968831

16 Jun 2026, 16:48 UTC94 views2 reactionsread 10 August 2026

С божьей помощью оплатила премиум щас реакции вам чотенькие еще поставлю

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.

Citation-graph rank

Citation-graph rank — 873,791 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

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.

Cite this entry

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Bench🦇🧟” (@lavka338), 39 subscribers as measured 10 August 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.