Telegram RegisterThe public register of Telegram
Telegram profile photo for Zoʻr Navo Bot

Bot

Zoʻr Navo Bot

@ZorNavoRobot

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

43,901monthly users

-3,837 since we began measuring on 14 August 2026

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

Register entry

Telegram ID6291110642
TypeBot
Username@ZorNavoRobot
First recorded14 August 2026
Last confirmed live4 November 2026
Measurements held41
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/ZorNavoRobot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

43,90151,37547,63814 August 2026 — 47,738 monthly users14 August 2026 — 47,738 monthly users15 August 2026 — 47,760 monthly users16 August 2026 — 47,764 monthly users17 August 2026 — 46,847 monthly users18 August 2026 — 47,563 monthly users23 August 2026 — 47,946 monthly users25 August 2026 — 48,110 monthly users25 August 2026 — 48,303 monthly users26 August 2026 — 48,446 monthly users27 August 2026 — 48,499 monthly users29 August 2026 — 49,133 monthly users31 August 2026 — 50,031 monthly users1 September 2026 — 50,403 monthly users5 September 2026 — 50,758 monthly users8 September 2026 — 51,164 monthly users11 September 2026 — 50,509 monthly users12 September 2026 — 51,313 monthly users14 September 2026 — 51,364 monthly users16 September 2026 — 51,375 monthly users18 September 2026 — 51,274 monthly users30 September 2026 — 49,742 monthly users6 October 2026 — 47,683 monthly users10 October 2026 — 46,362 monthly users13 October 2026 — 47,086 monthly users15 October 2026 — 47,040 monthly users16 October 2026 — 46,875 monthly users17 October 2026 — 46,382 monthly users19 October 2026 — 46,247 monthly users20 October 2026 — 45,920 monthly users22 October 2026 — 45,603 monthly users23 October 2026 — 45,356 monthly users24 October 2026 — 45,270 monthly users25 October 2026 — 45,167 monthly users26 October 2026 — 45,193 monthly users27 October 2026 — 44,959 monthly users28 October 2026 — 44,805 monthly users30 October 2026 — 44,408 monthly users1 November 2026 — 44,364 monthly users3 November 2026 — 44,242 monthly users4 November 2026 — 43,901 monthly users14 August 20264 November 2026
41 measurements spanning 83 days, net -3,837. 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 42,780–52,496 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 41
Measured (UTC)Monthly usersChange
4 Nov 2026, 20:3643,901-341
3 Nov 2026, 02:0544,242-122
1 Nov 2026, 00:2644,364-44
30 Oct 2026, 22:4444,408-397
28 Oct 2026, 22:1044,805-154
27 Oct 2026, 19:0644,959-234
26 Oct 2026, 19:0045,193+26
25 Oct 2026, 17:3045,167-103
24 Oct 2026, 18:4745,270-86
23 Oct 2026, 16:0645,356-247
22 Oct 2026, 19:4145,603-317
20 Oct 2026, 11:5845,920-327
19 Oct 2026, 14:3646,247-135
17 Oct 2026, 19:2546,382-493
16 Oct 2026, 01:3046,875-165
15 Oct 2026, 00:2647,040-46
13 Oct 2026, 19:4047,086+724
10 Oct 2026, 06:3846,362-1,321
6 Oct 2026, 00:5747,683-2,059
30 Sept 2026, 19:3849,742first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 6 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“Zoʻr Navo Bot” (@ZorNavoRobot), 43,901 monthly users as measured 4 November 2026. Telegram Register, tgregister.com/channel/ZorNavoRobot.

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.