Telegram RegisterThe public register of Telegram
Telegram profile photo for DuckyDice | 🎲

Bot

DuckyDice | 🎲

@DuckyDiceBot

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

18,300monthly users

+6,558 since we began measuring on 13 September 2026

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

Register entry

Telegram ID8736017382
TypeBot
Username@DuckyDiceBot
First recorded13 September 2026
Last confirmed live13 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/DuckyDiceBot

Topic

Gambling & betting — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

Growth

11,74218,30015,02113 September 2026 — 11,742 monthly users13 September 2026 — 11,742 monthly users14 September 2026 — 12,241 monthly users17 September 2026 — 13,235 monthly users19 September 2026 — 14,457 monthly users26 September 2026 — 17,451 monthly users4 October 2026 — 17,922 monthly users9 October 2026 — 18,300 monthly users13 September 20269 October 2026
8 measurements spanning 25 days, net +6,558. 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 10,758–19,284 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
9 Oct 2026, 02:3918,300+378
4 Oct 2026, 15:0117,922+471
26 Sept 2026, 09:3717,451+2,994
19 Sept 2026, 10:2014,457+1,222
17 Sept 2026, 00:4113,235+994
14 Sept 2026, 23:1712,241+499
13 Sept 2026, 20:4111,742no change
13 Sept 2026, 17:1711,742first 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 14 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 9 October 2026 — this entry's latest reading, not the date you are reading this.

“DuckyDice | 🎲” (@DuckyDiceBot), 18,300 monthly users as measured 9 October 2026. Telegram Register, tgregister.com/channel/DuckyDiceBot.

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.