Telegram RegisterThe public register of Telegram
Telegram profile photo for رواية 005 | 🦋

Channel

رواية 005 | 🦋

@uunxxu

Has discussion group

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

2,025subscribers

+320 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003342427463
TypeChannel
Username@uunxxu
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 September 2026
Last confirmed live26 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/uunxxu

Topic

Literature — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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,7052,0251,86511 August 2026 — 1,705 subscribers12 August 2026 — 1,707 subscribers15 August 2026 — 1,720 subscribers18 August 2026 — 1,738 subscribers22 August 2026 — 1,761 subscribers25 August 2026 — 1,788 subscribers28 August 2026 — 1,821 subscribers31 August 2026 — 1,852 subscribers4 September 2026 — 1,884 subscribers9 September 2026 — 1,916 subscribers13 September 2026 — 1,944 subscribers17 September 2026 — 1,968 subscribers21 September 2026 — 1,968 subscribers26 September 2026 — 2,025 subscribers11 August 202626 September 2026
14 measurements spanning 45 days, net +320. 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,657–2,073 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 07:202,025+57
21 Sept 2026, 02:341,968no change
17 Sept 2026, 03:581,968+24
13 Sept 2026, 00:001,944+28
9 Sept 2026, 08:551,916+32
4 Sept 2026, 00:411,884+32
31 Aug 2026, 07:261,852+31
28 Aug 2026, 10:081,821+33
25 Aug 2026, 17:521,788+27
22 Aug 2026, 10:341,761+23
18 Aug 2026, 21:021,738+18
15 Aug 2026, 10:561,720+13
12 Aug 2026, 09:221,707+2
11 Aug 2026, 20:151,705first 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“رواية 005 | 🦋” (@uunxxu), 2,025 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/uunxxu.

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.