Telegram RegisterThe public register of Telegram
Telegram profile photo for RDNO

Bot

RDNO

@RoyalDnoBot

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

34,795monthly users

-3,192 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID1014481227
TypeBot
Username@RoyalDnoBot
First recorded13 August 2026
Last confirmed live2 September 2026
Measurements held21
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/RoyalDnoBot

Growth

34,79537,98736,3916 August 2026 — 37,987 monthly users7 August 2026 — 37,812 monthly users9 August 2026 — 37,587 monthly users10 August 2026 — 37,436 monthly users12 August 2026 — 37,265 monthly users13 August 2026 — 37,265 monthly users13 August 2026 — 37,280 monthly users15 August 2026 — 37,005 monthly users16 August 2026 — 36,896 monthly users18 August 2026 — 36,977 monthly users19 August 2026 — 37,000 monthly users21 August 2026 — 37,086 monthly users22 August 2026 — 36,962 monthly users24 August 2026 — 36,916 monthly users25 August 2026 — 36,976 monthly users27 August 2026 — 36,631 monthly users28 August 2026 — 35,514 monthly users30 August 2026 — 36,105 monthly users31 August 2026 — 35,873 monthly users1 September 2026 — 35,722 monthly users2 September 2026 — 34,795 monthly users6 August 20262 September 2026
21 measurements spanning 27 days, net -3,192. 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 34,316–38,466 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 21
Measured (UTC)Monthly usersChange
2 Sept 2026, 17:4734,795-927
1 Sept 2026, 13:4735,722-151
31 Aug 2026, 11:1335,873-232
30 Aug 2026, 07:4436,105+591
28 Aug 2026, 05:3235,514-1,117
27 Aug 2026, 06:0436,631-345
25 Aug 2026, 04:1536,976+60
24 Aug 2026, 01:1836,916-46
22 Aug 2026, 10:3336,962-124
21 Aug 2026, 02:0337,086+86
19 Aug 2026, 23:2237,000+23
18 Aug 2026, 23:3236,977+81
16 Aug 2026, 19:3836,896-109
15 Aug 2026, 11:3737,005-275
13 Aug 2026, 23:4737,280+15
13 Aug 2026, 03:0837,265no change
12 Aug 2026, 17:2537,265-171
10 Aug 2026, 18:2837,436-151
9 Aug 2026, 21:1437,587-225
7 Aug 2026, 15:0537,812first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

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.

Mentions

Named by 5 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“RDNO” (@RoyalDnoBot), 34,795 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/RoyalDnoBot.

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.