Channel
Status_lorii
@status_lorii2020
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,466subscribers
-64 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001393732957 |
|---|---|
| Type | Channel |
| Username | @status_lorii2020 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/status_lorii2020 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 19:31 | 2,466 | -3 |
| 3 Nov 2026, 09:37 | 2,469 | -2 |
| 31 Oct 2026, 16:00 | 2,471 | -4 |
| 22 Oct 2026, 04:51 | 2,475 | -2 |
| 19 Oct 2026, 01:28 | 2,477 | -5 |
| 15 Oct 2026, 20:07 | 2,482 | -2 |
| 12 Oct 2026, 23:31 | 2,484 | -4 |
| 6 Oct 2026, 11:38 | 2,488 | -6 |
| 29 Sept 2026, 11:22 | 2,494 | -4 |
| 18 Sept 2026, 22:59 | 2,498 | -2 |
| 15 Sept 2026, 21:19 | 2,500 | no change |
| 14 Sept 2026, 13:58 | 2,500 | -6 |
| 10 Sept 2026, 20:16 | 2,506 | -1 |
| 5 Sept 2026, 19:59 | 2,507 | -6 |
| 1 Sept 2026, 13:27 | 2,513 | -4 |
| 29 Aug 2026, 11:04 | 2,517 | -3 |
| 26 Aug 2026, 17:53 | 2,520 | -4 |
| 24 Aug 2026, 00:23 | 2,524 | -2 |
| 20 Aug 2026, 16:38 | 2,526 | -4 |
| 16 Aug 2026, 19:30 | 2,530 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@music_qp2 · 26,693
Telegram ranks this channel #3 of 43 here — alongside 42 others — read 10 September 2026
@farshidhekmatiiiii · 21,526
Telegram ranks this channel #42 of 55 here — alongside 54 others — read 22 September 2026
@vidlmusic · 86,839
Telegram ranks this channel #59 of 59 here — alongside 58 others — read 17 August 2026
@florencestudio · 19,571
Telegram ranks this channel #69 of 76 here — alongside 75 others — read 2 October 2026
@qfisfjs · 103,748
Telegram ranks this channel #82 of 91 here — alongside 90 others — read 16 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Status_lorii” (@status_lorii2020), 2,466 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/status_lorii2020.
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.