Telegram RegisterThe public register of Telegram
Telegram profile photo for ZOʻR YUKLA BOT

Bot

ZOʻR YUKLA BOT

@ZoryuklaBot

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

33,520monthly users

+320 since we began measuring on 8 August 2026

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

Register entry

Telegram ID6638199340
TypeBot
Username@ZoryuklaBot
First recorded13 August 2026
Last confirmed live15 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/ZoryuklaBot

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 95% 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

31,37134,49632,933.58 August 2026 — 33,200 monthly users9 August 2026 — 33,046 monthly users10 August 2026 — 33,061 monthly users11 August 2026 — 33,136 monthly users12 August 2026 — 32,781 monthly users13 August 2026 — 32,781 monthly users14 August 2026 — 33,321 monthly users16 August 2026 — 33,309 monthly users17 August 2026 — 33,347 monthly users19 August 2026 — 33,401 monthly users20 August 2026 — 33,384 monthly users21 August 2026 — 33,405 monthly users23 August 2026 — 33,434 monthly users24 August 2026 — 33,675 monthly users25 August 2026 — 33,769 monthly users26 August 2026 — 33,837 monthly users27 August 2026 — 33,865 monthly users28 August 2026 — 33,958 monthly users29 August 2026 — 34,034 monthly users31 August 2026 — 34,151 monthly users1 September 2026 — 34,242 monthly users2 September 2026 — 33,966 monthly users3 September 2026 — 34,431 monthly users5 September 2026 — 34,468 monthly users8 September 2026 — 34,496 monthly users11 September 2026 — 34,408 monthly users13 September 2026 — 33,948 monthly users15 September 2026 — 34,250 monthly users16 September 2026 — 34,248 monthly users19 September 2026 — 33,832 monthly users26 September 2026 — 33,447 monthly users4 October 2026 — 31,879 monthly users9 October 2026 — 31,682 monthly users13 October 2026 — 31,804 monthly users14 October 2026 — 31,724 monthly users16 October 2026 — 31,371 monthly users17 October 2026 — 31,588 monthly users18 October 2026 — 31,687 monthly users19 October 2026 — 31,799 monthly users20 October 2026 — 31,908 monthly users21 October 2026 — 31,916 monthly users22 October 2026 — 31,937 monthly users25 October 2026 — 31,644 monthly users26 October 2026 — 32,084 monthly users27 October 2026 — 32,167 monthly users28 October 2026 — 32,166 monthly users28 October 2026 — 32,203 monthly users30 October 2026 — 32,237 monthly users31 October 2026 — 32,195 monthly users1 November 2026 — 32,346 monthly users2 November 2026 — 32,411 monthly users3 November 2026 — 32,412 monthly users5 November 2026 — 32,445 monthly users6 November 2026 — 32,607 monthly users7 November 2026 — 32,733 monthly users8 November 2026 — 32,903 monthly users10 November 2026 — 33,210 monthly users12 November 2026 — 33,320 monthly users15 November 2026 — 33,520 monthly users33,5208 August 202615 November 2026
59 measurements spanning 99 days, net +320. 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 30,902–34,965 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 59
Measured (UTC)Monthly usersChange
15 Nov 2026, 08:5733,520+200
12 Nov 2026, 00:1133,320+110
10 Nov 2026, 04:0733,210+307
8 Nov 2026, 20:3632,903+170
7 Nov 2026, 13:3032,733+126
6 Nov 2026, 12:5032,607+162
5 Nov 2026, 14:0732,445+33
3 Nov 2026, 16:3632,412+1
2 Nov 2026, 18:0832,411+65
1 Nov 2026, 20:4632,346+151
31 Oct 2026, 00:0632,195-42
30 Oct 2026, 03:1832,237+34
28 Oct 2026, 23:4632,203+37
28 Oct 2026, 01:3632,166-1
27 Oct 2026, 02:5632,167+83
26 Oct 2026, 04:1032,084+440
25 Oct 2026, 02:2731,644-293
22 Oct 2026, 23:5031,937+21
21 Oct 2026, 21:1731,916+8
20 Oct 2026, 17:3931,908first 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 20 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“ZOʻR YUKLA BOT” (@ZoryuklaBot), 33,520 monthly users as measured 15 November 2026. Telegram Register, tgregister.com/channel/ZoryuklaBot.

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.