Telegram RegisterThe public register of Telegram
Telegram profile photo for luxuria

Channel

luxuria

@luxuria_a

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,654subscribers

+9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002246208099
TypeChannel
Username@luxuria_a
CreatedBetween 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 September 2026
Last confirmed live25 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/luxuria_a

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

1,6451,6641,654.57 August 2026 — 1,645 subscribers8 August 2026 — 1,647 subscribers11 August 2026 — 1,650 subscribers14 August 2026 — 1,648 subscribers17 August 2026 — 1,646 subscribers20 August 2026 — 1,655 subscribers24 August 2026 — 1,664 subscribers27 August 2026 — 1,661 subscribers30 August 2026 — 1,664 subscribers6 September 2026 — 1,661 subscribers11 September 2026 — 1,659 subscribers15 September 2026 — 1,656 subscribers25 September 2026 — 1,656 subscribers25 September 2026 — 1,654 subscribers1,6547 August 202625 September 2026
14 measurements spanning 49 days, net +9. 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 1,642–1,667 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 06:221,654-2
25 Sept 2026, 03:121,656no change
15 Sept 2026, 07:151,656-3
11 Sept 2026, 17:191,659-2
6 Sept 2026, 19:371,661-3
30 Aug 2026, 17:051,664+3
27 Aug 2026, 10:141,661-3
24 Aug 2026, 09:541,664+9
20 Aug 2026, 14:471,655+9
17 Aug 2026, 19:581,646-2
14 Aug 2026, 16:461,648-2
11 Aug 2026, 11:391,650+3
8 Aug 2026, 07:461,647+2
7 Aug 2026, 16:011,645first 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.

Forward network

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.

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“luxuria” (@luxuria_a), 1,654 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/luxuria_a.

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.