Telegram RegisterThe public register of Telegram

Bot

Adliya xabari

@adliyaxabaribot

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

50,193monthly users

+30,405 since we began measuring on 28 September 2026

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

Register entry

Telegram ID8187820607
TypeBot
Username@adliyaxabaribot
First recorded28 September 2026
Last confirmed live17 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/adliyaxabaribot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 70% 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

15,18550,19332,68928 September 2026 — 19,788 monthly users28 September 2026 — 19,788 monthly users4 October 2026 — 16,903 monthly users9 October 2026 — 16,368 monthly users13 October 2026 — 16,024 monthly users20 October 2026 — 15,256 monthly users23 October 2026 — 15,185 monthly users27 October 2026 — 15,624 monthly users29 October 2026 — 15,982 monthly users1 November 2026 — 26,350 monthly users4 November 2026 — 30,292 monthly users7 November 2026 — 38,073 monthly users11 November 2026 — 40,105 monthly users14 November 2026 — 47,876 monthly users17 November 2026 — 50,193 monthly users28 September 202617 November 2026
15 measurements spanning 51 days, net +30,405. 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 9,934–55,444 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
17 Nov 2026, 20:2850,193+2,317
14 Nov 2026, 13:1847,876+7,771
11 Nov 2026, 18:0440,105+2,032
7 Nov 2026, 08:1838,073+7,781
4 Nov 2026, 13:5930,292+3,942
1 Nov 2026, 16:5726,350+10,368
29 Oct 2026, 12:3415,982+358
27 Oct 2026, 11:0515,624+439
23 Oct 2026, 05:0615,185-71
20 Oct 2026, 00:0715,256-768
13 Oct 2026, 09:3516,024-344
9 Oct 2026, 06:3716,368-535
4 Oct 2026, 21:2116,903-2,885
28 Sept 2026, 02:0019,788no change
28 Sept 2026, 01:4719,788first 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.

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

“Adliya xabari” (@adliyaxabaribot), 50,193 monthly users as measured 17 November 2026. Telegram Register, tgregister.com/channel/adliyaxabaribot.

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.