Telegram RegisterThe public register of Telegram
Telegram profile photo for Meteor dubbing

Bot

Meteor dubbing

@meteor_dubbing_bot

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

18,519monthly users

-4,253 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8733032220
TypeBot
Username@meteor_dubbing_bot
First recorded16 August 2026
Last confirmed live29 August 2026
Measurements held14
Confirmed unchanged2 times, most recently 29 August 2026
On Telegramt.me/meteor_dubbing_bot

Growth

18,51922,77220,645.57 August 2026 — 22,772 monthly users9 August 2026 — 22,718 monthly users11 August 2026 — 22,337 monthly users12 August 2026 — 22,142 monthly users14 August 2026 — 21,517 monthly users15 August 2026 — 21,222 monthly users16 August 2026 — 21,222 monthly users17 August 2026 — 20,671 monthly users20 August 2026 — 20,501 monthly users22 August 2026 — 19,444 monthly users24 August 2026 — 19,365 monthly users25 August 2026 — 19,483 monthly users26 August 2026 — 19,250 monthly users28 August 2026 — 18,519 monthly users7 August 202628 August 2026
14 measurements spanning 21 days, net -4,253. 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 17,881–23,410 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
28 Aug 2026, 18:2218,519-731
26 Aug 2026, 20:1219,250-233
25 Aug 2026, 18:2619,483+118
24 Aug 2026, 16:1219,365-79
22 Aug 2026, 22:4719,444-1,057
20 Aug 2026, 13:2720,501-170
17 Aug 2026, 10:3920,671-551
16 Aug 2026, 03:1921,222no change
15 Aug 2026, 19:2821,222-295
14 Aug 2026, 12:0721,517-625
12 Aug 2026, 23:3422,142-195
11 Aug 2026, 01:3822,337-381
9 Aug 2026, 02:2122,718-54
7 Aug 2026, 20:4722,772first 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 1 registered channel — 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 28 August 2026 — this entry's latest reading, not the date you are reading this.

“Meteor dubbing” (@meteor_dubbing_bot), 18,519 monthly users as measured 28 August 2026. Telegram Register, tgregister.com/channel/meteor_dubbing_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.