Telegram RegisterThe public register of Telegram
Telegram profile photo for DINO PINK | #BOT

Bot

DINO PINK | #BOT

@dinopinkxrobot

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

12,851monthly users

+319 since we began measuring on 10 August 2026

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

Register entry

Telegram ID7622686093
TypeBot
Username@dinopinkxrobot
First recorded20 August 2026
Last confirmed live5 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/dinopinkxrobot

Growth

12,21013,29712,753.510 August 2026 — 12,532 monthly users12 August 2026 — 12,454 monthly users14 August 2026 — 12,248 monthly users16 August 2026 — 12,228 monthly users17 August 2026 — 12,283 monthly users19 August 2026 — 12,210 monthly users20 August 2026 — 12,210 monthly users22 August 2026 — 12,624 monthly users24 August 2026 — 12,873 monthly users25 August 2026 — 13,076 monthly users26 August 2026 — 13,205 monthly users28 August 2026 — 12,861 monthly users31 August 2026 — 13,297 monthly users1 September 2026 — 12,983 monthly users3 September 2026 — 13,236 monthly users5 September 2026 — 12,851 monthly users12,85110 August 20265 September 2026
16 measurements spanning 26 days, net +319. 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,047–13,460 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
5 Sept 2026, 07:3812,851-385
3 Sept 2026, 09:1313,236+253
1 Sept 2026, 06:4412,983-314
31 Aug 2026, 09:4313,297+436
28 Aug 2026, 07:1612,861-344
26 Aug 2026, 09:5413,205+129
25 Aug 2026, 06:5513,076+203
24 Aug 2026, 08:1512,873+249
22 Aug 2026, 19:1712,624+414
20 Aug 2026, 20:3012,210no change
19 Aug 2026, 10:3512,210-73
17 Aug 2026, 13:1312,283+55
16 Aug 2026, 04:1512,228-20
14 Aug 2026, 15:5512,248-206
12 Aug 2026, 06:4812,454-78
10 Aug 2026, 12:1612,532first 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 18 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“DINO PINK | #BOT” (@dinopinkxrobot), 12,851 monthly users as measured 5 September 2026. Telegram Register, tgregister.com/channel/dinopinkxrobot.

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.