Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 19 August 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Views per post sit far above this size band
8,870 average views per post against 17,371 subscribers — an engagement rate of 51.1%. Across the 5,595 registered channels in the same cohort — 10,000–31,618 subscribers, posting mainly in English — the middle half sit between 1.93% and 10.6%, with a median of 5.25%.
What this was computed from
Window
30 days (24 August 2026 – 23 September 2026)
Posts measured
16 of 16 published in the window (0 exact, 16 rounded by Telegram)
Views totalled
141,890
Mature posts only
52.0% over 15 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 23 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Growth
33 measurements spanning 42 days, net +927. 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 16,304–17,510 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
17 Sept 2026, 04:56
17,371
+124
15 Sept 2026, 04:59
17,247
+35
13 Sept 2026, 14:36
17,212
-1
11 Sept 2026, 20:36
17,213
+15
9 Sept 2026, 11:41
17,198
-3
6 Sept 2026, 01:39
17,201
-10
3 Sept 2026, 20:02
17,211
+48
2 Sept 2026, 12:56
17,163
-5
1 Sept 2026, 13:25
17,168
+26
31 Aug 2026, 12:04
17,142
+3
30 Aug 2026, 08:49
17,139
+51
29 Aug 2026, 08:05
17,088
-4
28 Aug 2026, 06:54
17,092
+4
27 Aug 2026, 10:04
17,088
+2
26 Aug 2026, 06:48
17,086
+6
25 Aug 2026, 04:56
17,080
+4
24 Aug 2026, 01:07
17,076
+226
22 Aug 2026, 09:47
16,850
+257
21 Aug 2026, 01:22
16,593
-8
19 Aug 2026, 23:51
16,601
first reading
Engagement
63 posts held, back to 14 July 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 54 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
51.1%
avg views ÷ 17,371 subscribers
Avg views / post
8,870
16 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
16
of 63 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. It is computed over the 12 of 16 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 2 September 2026
Posts held
63 (14 July 2026 – 2 September 2026)
Views total
141,890
Reactions total
0
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 09:29 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
Video runtime
58s
Average length
10s
Measured directly from 6 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.
Telegram Stars
Stars received
479
across the posts below
Posts paid on
44
of 63 we hold a reading for · 70%
Most on one post
177
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @telelakel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 63 most recent posts we hold for this entry, published 14 July 2026 to 2 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
💎 In the new Telegram Beta for iOS v12.10.0 (34738), Gram Wallet has been added. It doesn't work yet and is currently view-only.
First 5 transfers each day are free, the rest cost almost nothing.
Previously mentioned:
[View 1], [View 2]
@telelakel | #new_tgbeta
On ads.telegram.org, the restriction on displaying advertisements in Israel and Palestine that were paid for with Gram (TON) has been removed.
However, the restriction remains in place for Ukraine and Russia.
@telelakel
Verification has been removed from the third-party Wallet (@wallet).
The new built-in Gram Wallet is currently available only to Telegram developers. Regular users don't have access to it yet.
@telelakel
The names of owners of IOI and IOAI participant gifts will now be displayed when the gifts have been resold to other users.
Previously, «IOI/IOAI 2026 Winner» was displayed instead of the owner's name. This will remain unchanged for participants who still own their gifts, even if the gift is displayed on their profile.
For resold gifts, the name of the new owner who purchased the gift will now be displayed instead.…
Soon, you will be able to apply to test the new «Serverless» feature in the BotFather MiniApp.
Join the waitlist — we grant access gradually, prioritizing Premium users with popular bots.
For now, you can only apply on the test server (no one will answer you there).
Previously mentioned:
[View 1], [View 2], [View 3], [View 4]
@telelakel
Future versions Telegram for iOS will no longer support iOS 13.
Telegram is ending support for older iOS versions. You will now need iOS 15.0 or later to use future Telegram updates.
@telelakel
In Telegram Beta for Android v12.10.2 (7060), Web Proxy has been added.
To add a new proxy, go to Settings → Data and Storage → Proxy Settings → Web Proxy.
Alternatively, you can open a link in the format "t.me/webproxy?server=" or "tg://webproxy?server=" with the corresponding data.
Previously mentioned:
[View 1], [View 2], [View 3]
@telelakel | #new_tgbeta
In the code of Telegram Beta for iOS v12.10.0 (34659), the implementation of Web Proxy has been added.
The entire process takes place directly inside Telegram using WKWebView, without opening the external Safari browser.
Previously mentioned:
[View 1], [View 2]
@telelakel | #new_tgbeta
💎 After analyzing the code of Telegram’s upcoming TON (Gram) Wallet and its smart contract, we can already see what is being prepared.
The wallet will support TON, Jettons, and NFTs. Users will be able to view their balance and transaction history, as well as receive and send assets. TON Connect will also be available, allowing the wallet to connect to websites and dApps on the TON network and confirm transactions.
…
Showing the 12 most recent of 63 posts we hold for @telelakel. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@telelakel edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
8 August 2026
Most recent edit
20 August 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 60 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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.
Mentions
Named by 254 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“teleLakel” (@telelakel), 17,371 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/telelakel.
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.