Telegram RegisterThe public register of Telegram
Telegram profile photo for Muz Navo Bot

Bot

Muz Navo Bot

@MuznavoBot

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

11,653monthly users

+57 since we began measuring on 12 August 2026

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

Register entry

Telegram ID5755069681
TypeBot
Username@MuznavoBot
First recorded21 August 2026
Last confirmed live27 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/MuznavoBot

Growth

11,59611,83111,713.512 August 2026 — 11,596 monthly users12 August 2026 — 11,782 monthly users14 August 2026 — 11,776 monthly users15 August 2026 — 11,807 monthly users17 August 2026 — 11,677 monthly users18 August 2026 — 11,831 monthly users19 August 2026 — 11,824 monthly users20 August 2026 — 11,793 monthly users21 August 2026 — 11,793 monthly users21 August 2026 — 11,784 monthly users23 August 2026 — 11,815 monthly users27 August 2026 — 11,653 monthly users11,65312 August 202627 August 2026
12 measurements spanning 15 days, net +57. 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,561–11,866 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
27 Aug 2026, 01:4311,653-162
23 Aug 2026, 12:2911,815+31
21 Aug 2026, 22:0611,784-9
21 Aug 2026, 10:0711,793no change
20 Aug 2026, 17:0411,793-31
19 Aug 2026, 15:3711,824-7
18 Aug 2026, 12:4511,831+154
17 Aug 2026, 09:4711,677-130
15 Aug 2026, 15:1711,807+31
14 Aug 2026, 01:0811,776-6
12 Aug 2026, 22:0511,782+186
12 Aug 2026, 05:1611,596first 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“Muz Navo Bot” (@MuznavoBot), 11,653 monthly users as measured 27 August 2026. Telegram Register, tgregister.com/channel/MuznavoBot.

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.