Channel
.
@KryptonianEN
On this record: Growth · Engagement · Cite this entry
6,107subscribers
-114 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002047964045 |
|---|---|
| Type | Channel |
| Username | @KryptonianEN |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/KryptonianEN |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 07:28 | 6,107 | -17 |
| 29 Aug 2026, 11:54 | 6,124 | no change |
| 27 Aug 2026, 10:35 | 6,124 | -10 |
| 24 Aug 2026, 04:13 | 6,134 | -18 |
| 20 Aug 2026, 19:22 | 6,152 | -15 |
| 17 Aug 2026, 17:36 | 6,167 | -12 |
| 14 Aug 2026, 20:25 | 6,179 | -15 |
| 11 Aug 2026, 17:17 | 6,194 | -19 |
| 8 Aug 2026, 06:52 | 6,213 | -8 |
| 7 Aug 2026, 12:36 | 6,221 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“.” (@KryptonianEN), 6,107 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/KryptonianEN.
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.