Channel
_princess.avrora_
@lloollkkee
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,104subscribers
-29 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001472216662 |
|---|---|
| Type | Channel |
| Username | @lloollkkee |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/lloollkkee |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 10:20 | 5,104 | -7 |
| 12 Sept 2026, 23:41 | 5,111 | -11 |
| 8 Sept 2026, 23:36 | 5,122 | +2 |
| 3 Sept 2026, 08:55 | 5,120 | +1 |
| 1 Sept 2026, 11:52 | 5,119 | no change |
| 31 Aug 2026, 00:05 | 5,119 | -2 |
| 25 Aug 2026, 01:54 | 5,121 | -5 |
| 21 Aug 2026, 16:12 | 5,126 | -1 |
| 18 Aug 2026, 21:45 | 5,127 | -4 |
| 16 Aug 2026, 06:07 | 5,131 | -2 |
| 15 Aug 2026, 09:45 | 5,133 | 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.
@yanyaru · 57,464
Telegram ranks this channel #7 of 51 here — alongside 50 others — read 6 September 2026
@evkasup13 · 103,801
Telegram ranks this channel #28 of 54 here — alongside 53 others — read 15 August 2026
@umkatgk · 52,130
Telegram ranks this channel #29 of 53 here — alongside 52 others — read 24 August 2026
@kkkkiiirraaa · 36,683
Telegram ranks this channel #32 of 44 here — alongside 43 others — read 12 September 2026
@lovatikann · 49,079
Telegram ranks this channel #43 of 65 here — alongside 64 others — read 25 August 2026
@helnns · 68,574
Telegram ranks this channel #50 of 59 here — alongside 58 others — read 20 August 2026
@dankakriv · 53,731
Telegram ranks this channel #51 of 57 here — alongside 56 others — read 24 August 2026
@duoclub · 65,986
Telegram ranks this channel #57 of 72 here — alongside 71 others — read 22 August 2026
This channel appears in 8 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“_princess.avrora_” (@lloollkkee), 5,104 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/lloollkkee.
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.