Telegram RegisterThe public register of Telegram
Telegram profile photo for Mirabelle Bot

Bot

Mirabelle Bot

@MiirabelleBOT

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

16,320monthly users

+4,437 since we began measuring on 21 August 2026

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

Register entry

Telegram ID8881096489
TypeBot
Username@MiirabelleBOT
First recorded21 August 2026
Last confirmed live5 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/MiirabelleBOT

Growth

11,88316,32014,101.521 August 2026 — 11,883 monthly users21 August 2026 — 11,883 monthly users23 August 2026 — 12,522 monthly users25 August 2026 — 13,672 monthly users26 August 2026 — 13,941 monthly users26 August 2026 — 14,258 monthly users27 August 2026 — 14,473 monthly users28 August 2026 — 14,692 monthly users29 August 2026 — 15,040 monthly users30 August 2026 — 15,199 monthly users1 September 2026 — 15,317 monthly users1 September 2026 — 15,422 monthly users3 September 2026 — 15,875 monthly users5 September 2026 — 16,320 monthly users21 August 20265 September 2026
14 measurements spanning 14 days, net +4,437. 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 11,217–16,986 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
5 Sept 2026, 01:5816,320+445
3 Sept 2026, 09:2215,875+453
1 Sept 2026, 23:3815,422+105
1 Sept 2026, 01:0815,317+118
30 Aug 2026, 21:3415,199+159
29 Aug 2026, 21:3415,040+348
28 Aug 2026, 20:3314,692+219
27 Aug 2026, 21:1914,473+215
26 Aug 2026, 21:5614,258+317
26 Aug 2026, 00:3613,941+269
25 Aug 2026, 02:2813,672+1,150
23 Aug 2026, 19:0512,522+639
21 Aug 2026, 18:0011,883no change
21 Aug 2026, 17:4511,883first 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Mirabelle Bot” (@MiirabelleBOT), 16,320 monthly users as measured 5 September 2026. Telegram Register, tgregister.com/channel/MiirabelleBOT.

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.