Telegram RegisterThe public register of Telegram
Telegram profile photo for ROBÔ FORTUNE DRAGON 🐲

Channel

ROBÔ FORTUNE DRAGON 🐲

@robofortunedragon

On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry

611subscribers

-36 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002031723643
TypeChannel
Username@robofortunedragon
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live5 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/robofortunedragon

Growth

6116476297 August 2026 — 647 subscribers8 August 2026 — 647 subscribers8 August 2026 — 646 subscribers15 August 2026 — 637 subscribers22 August 2026 — 624 subscribers29 August 2026 — 619 subscribers5 September 2026 — 611 subscribers7 August 20265 September 2026
7 measurements spanning 29 days, net -36. 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 606–652 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 11:36611-8
29 Aug 2026, 13:07619-5
22 Aug 2026, 18:29624-13
15 Aug 2026, 03:17637-9
8 Aug 2026, 13:45646-1
8 Aug 2026, 02:47647no change
7 Aug 2026, 13:40647first reading

Engagement

1 post held, back to 8 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 1 post for this entry, the most recent from 8 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
53s
Average length
53s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

8 Jul 2026, 15:49 UTC45 viewsread 8 August 2026
Video

🟥🟥🟥🟥🟥🟥 🟥🟥🟥🟥✅ ⚠️ GRUPO EXCLUSIVO PARA +18 Aqui você vai realmente ganhar de forma 100% Confiável. 🤔 Mas para isso, você precisa estar na mesma plataforma que eu. 1️⃣ CADASTRE-SE NA BETUXO 🎁 CADASTRE-SE AQUI E GANHE 2️⃣ APP RTP SLOTS GRÁTIS 🎁 CLIQUE AQUI PARA ACESSAR ✔️ Recomendo começar com uma banca de pelo menos R$100,00 para um gerenciamento correto.

Showing the 1 most recent of 1 post we hold for @robofortunedragon. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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.

“ROBÔ FORTUNE DRAGON 🐲” (@robofortunedragon), 611 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/robofortunedragon.

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.