Channel
@telelight_app_en
On this record: Growth · Engagement · Posts · Citations · Cite this entry
589subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001377970859 |
|---|---|
| Type | Channel |
| Username | @telelight_app_en |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/telelight_app_en |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 03:20 | 589 | +1 |
| 7 Aug 2026, 02:16 | 588 | no change |
| 7 Aug 2026, 02:05 | 588 | first reading |
20 posts held, back to 6 June 2023 — 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 pageof 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 20 posts for this entry, the most recent from 17 July 2025. An engagement rate over an empty window would be a number about nothing.
New Production Release Is Downloadable! A new Telelight update (T11.9.0B58449) is ready for download in production channel. This update is the same as latest Open Beta release that has now been tested for weeks for stability and bug-fix checks. It is now Production ready and includes latest source codes and many bug fixes. For those who haven't updated yet, you can do so here: https://play.google.com/store/apps/det…
New Open Beta 11.9.0 Is Out! Latest Beta version of Telelight using the Telegram source code 11.9.0 is currently out for download and ready to be tested by Beta testers. All opted-in users can now download the Telelight Open Beta T11.9.0B58449. We have around ~300 beta testers. Please send the bugs you find to @TelelightBot so we can promote a bug-free version of this beta to production, as soon as possible. If yo…
OK, The Google Play keeps rejecting our beta update despite it being ready; For some awkward reasons e.g impersonation allegation in the app's name ... found by Google after almost 3 years of its release date! We are trying to get the update accepted soon.
New Beta Update On Its Way! We've been working for weeks on the latest bunch of update the Telegram source code has received in recent months. Finally the most recent beta of Telelight based on source code version 11.9.0 is in its final stages and will be released in a few days. Thank you all loyal users of Telelight for your patience. Stay tuned ...
New Production Release Is Here! The latest Telelight update (T11.0.0B51469) is now live in production channel. This update is the same as latest Open Beta release that has now been tested for weeks for stability and bug-fix checks. It is now Production ready and includes latest source codes and many bug-fixes. For those who haven't updated yet, you can do so here: https://play.google.com/store/apps/details?id=org.t…
Open Beta Fix T11.0.0B51469 Just Released! Since the previous Open Beta release, we were working on a fix for the bugs reported on that. The fix is ready now and it uses the same Telegram source 11.0.0 as the previous Open Beta, but it features some crucial fixes to Telelight-specific bugs reported by our testers from around the world. This Beta is release candidate, meaning that if our ~250 beta testers don't find…
New Open Beta 11.0.0 Now Available! Latest Beta version of Telelight based on Telegram source code 11.0.0 is currently ready to be tested by Beta testers. All opted-in users can now download the Telelight Open Beta T11.0.0B51449. We are asking for bug reports from our ~220 beta testers regarding this version. Please send them to @TelelightBot so we can promote a bug-free version of this beta to production, as soon …
New Production Release Has Been Available For A While Now! If you haven't noticed yet, Telelight T10.10.1B45849 has been available in public production for some weeks now. In case you still have not updated your Telelight, you can do so from: https://play.google.com/store/apps/details?id=org.telelightpro.messenger Full Changelog Compared to Prev Production Release (10.0.1): - Updated to Telegram source code of 10.1…
Open Beta 10.10.1 Now Available! Due to high number of source code pushes by Telegram to Github, we decided to jump the 10.9.1 source code and go with 10.10.1 source code. All opted-in users can now download the Telelight Open Beta T10.10.1B45849. We appreciate any problems report from our ~200 beta testers regarding this version. Please send them to @TelelightBot so we can move faster to production release. Full …
Beta 10.9.1 In Progress! Since Telegram has released several updates and pushed several source code changes to GitHub in the past 2 months, we decided to first upgrade the current Beta build from version 10.3.9 to latest version 10.9.1. This process has been started and is in progress. We will then work on stabilizing that Beta build and releasing it into the Production channel.
New Beta Version Based on Telegram 10.3.2 Is Out! All opted-in users can now download the Telelight Open Beta T10.3.2B41469. This Beta is based on Telegram 10.3.2 source code. We appreciate any problems report from our ~200 beta testers regarding this version. Please send them to @TelelightBot so we can move faster to production release. Full Changelog Compared to Current Production Release (10.0.1): - Updated to …
New version & Happy New Year! Latest Beta version of Telelight based on Telegram source code 10.3.2 is currently being tested by internal testers and soon will be released to Google Play's Beta channel, for all beta testers.
Showing the 12 most recent of 20 posts we hold for @telelight_app_en. 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 — 371,683 of 1,336,469entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Telelight, Accessible Telegram-Official Channel” (@telelight_app_en), 589 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/telelight_app_en.
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.