Telegram RegisterThe public register of Telegram
Telegram profile photo for >_< лак облез

Channel

>_< лак облез

@lakoblez9

On this record: Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry

354subscribers

+10 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002873873896
TypeChannel
Username@lakoblez9
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live31 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/lakoblez9

Growth

3443543498 August 2026 — 344 subscribers8 August 2026 — 344 subscribers16 August 2026 — 345 subscribers24 August 2026 — 351 subscribers31 August 2026 — 354 subscribers8 August 202631 August 2026
5 measurements spanning 23 days, net +10. 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 343–356 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 10:25354+3
24 Aug 2026, 15:47351+6
16 Aug 2026, 20:16345+1
8 Aug 2026, 07:01344no change
8 Aug 2026, 06:48344first reading

Engagement

10 posts held, back to 1 May 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 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 10 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

897 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 25.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 543864934240566093222725.3%
custom 520408604720130676716218.1%
custom 540485602002967775015216.9%
custom 545885462520765708514816.5%
custom 5377631837248050880899.92%
custom 5370766641263027059647.13%
custom 5341333333462769908283.12%
custom 5242313553943237766131.45%
custom 5382025623151599556131.45%
custom 528278071003632847710.111%

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 10 of the 10 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 897 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 1 May 2026 to 15 July 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

15 Jul 2026, 13:03 UTC179 views51 reactionsread 8 August 2026
Forwarded from @swaaagrizzPhoto

самоцвет00001

custom 545885462520765708525custom 520408604720130676713custom 53413333334627699088custom 52423135539432377665

9 Jul 2026, 09:41 UTC382 views112 reactionsread 8 August 2026
Photo

🤩😋🤩🏳️‍🌈🕸

custom 545885462520765708557custom 520408604720130676730custom 534133333346276990817custom 52423135539432377668

5 Jul 2026, 11:47 UTC428 views26 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

custom 520408604720130676713custom 54386493424056609326custom 54588546252076570854custom 53413333334627699083

23 Jun 2026, 18:35 UTC692 views139 reactionsread 8 August 2026
Photo

🌟🚗🔘🥹 🐽✨🧛‍♂🪄🧍‍♀🖤🐞

custom 543864934240566093264custom 545885462520765708539custom 540485602002967775025custom 520408604720130676711

21 Jun 2026, 09:20 UTC595 views67 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 543864934240566093239custom 520408604720130676718custom 54048560200296777506custom 54588546252076570854

9 Jun 2026, 07:58 UTC≈4,280 views153 reactionsread 8 August 2026
Photo

у меня севодня др🥳🙂🎂 чпасибо друзья и подписчики

custom 540485602002967775063custom 543864934240566093243custom 537076664126302705930custom 520408604720130676713custom 53776318372480508804

11 May 2026, 07:51 UTC≈2,060 views103 reactionsread 8 August 2026
Photo

🎶

custom 520408604720130676747custom 540485602002967775028custom 537763183724805088013custom 545885462520765708512custom 53820256231515995562custom 53707666412630270591

5 May 2026, 16:50 UTC817 views86 reactionsread 8 August 2026
Photo

🖤🖤🌟🌟🌟🌟🎀🧸🖤🌟

custom 537763183724805088036custom 543864934240566093221custom 540485602002967775015custom 52040860472013067679custom 53820256231515995563custom 53707666412630270592

3 May 2026, 13:48 UTC741 views72 reactionsread 8 August 2026
Photo

4/4 🗂

custom 543864934240566093234custom 537076664126302705922custom 52040860472013067678custom 53820256231515995568

1 May 2026, 21:05 UTC684 views88 reactionsread 8 August 2026
Photo

🤩🤩🍄

custom 537763183724805088036custom 543864934240566093220custom 540485602002967775015custom 53707666412630270599custom 54588546252076570857custom 52827807100363284771

Showing the 10 most recent of 10 posts we hold for @lakoblez9. 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.

Forward network

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.

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

“>_< лак облез” (@lakoblez9), 354 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/lakoblez9.

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.