Telegram RegisterThe public register of Telegram
Telegram profile photo for Rise of Cinder Duck

Bot

Rise of Cinder Duck

@RCD_Web3_bot

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

13,767monthly users

-5,622 since we began measuring on 6 August 2026

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

Register entry

Telegram ID8264677840
TypeBot
Username@RCD_Web3_bot
First recorded16 August 2026
Last confirmed live25 August 2026
Measurements held16
Confirmed unchanged2 times, most recently 25 August 2026
On Telegramt.me/RCD_Web3_bot

Growth

13,76719,38916,5786 August 2026 — 19,389 monthly users7 August 2026 — 19,274 monthly users8 August 2026 — 19,242 monthly users9 August 2026 — 19,292 monthly users11 August 2026 — 19,303 monthly users12 August 2026 — 19,279 monthly users13 August 2026 — 19,263 monthly users15 August 2026 — 19,237 monthly users16 August 2026 — 19,003 monthly users16 August 2026 — 19,003 monthly users17 August 2026 — 18,092 monthly users19 August 2026 — 17,756 monthly users20 August 2026 — 16,628 monthly users21 August 2026 — 16,169 monthly users23 August 2026 — 14,082 monthly users24 August 2026 — 13,767 monthly users6 August 202624 August 2026
16 measurements spanning 19 days, net -5,622. 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 12,924–20,232 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
24 Aug 2026, 23:0413,767-315
23 Aug 2026, 09:3414,082-2,087
21 Aug 2026, 17:2816,169-459
20 Aug 2026, 16:1416,628-1,128
19 Aug 2026, 16:4317,756-336
17 Aug 2026, 17:4418,092-911
16 Aug 2026, 20:5419,003no change
16 Aug 2026, 15:1719,003-234
15 Aug 2026, 02:1519,237-26
13 Aug 2026, 15:4819,263-16
12 Aug 2026, 15:0619,279-24
11 Aug 2026, 14:3219,303+11
9 Aug 2026, 17:0119,292+50
8 Aug 2026, 15:1319,242-32
7 Aug 2026, 15:4519,274-115
6 Aug 2026, 03:3219,389first 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.

Mentions

Named by 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Rise of Cinder Duck” (@RCD_Web3_bot), 13,767 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/RCD_Web3_bot.

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.