Telegram RegisterThe public register of Telegram
Telegram profile photo for IzlaydiBot 🎵

Bot

IzlaydiBot 🎵

@OnashkaBot

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

75,477monthly users

-18,126 since we began measuring on 29 August 2026

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

Register entry

Telegram ID1004016702
TypeBot
Username@OnashkaBot
First recorded29 August 2026
Last confirmed live26 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/OnashkaBot

Topic

Music — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 why it has no browse page of its own yet.

Growth

75,47793,60384,54029 August 2026 — 93,603 monthly users29 August 2026 — 93,603 monthly users30 August 2026 — 93,390 monthly users31 August 2026 — 93,500 monthly users1 September 2026 — 93,263 monthly users2 September 2026 — 93,130 monthly users3 September 2026 — 91,291 monthly users6 September 2026 — 92,884 monthly users9 September 2026 — 91,918 monthly users12 September 2026 — 87,163 monthly users13 September 2026 — 85,739 monthly users15 September 2026 — 84,577 monthly users17 September 2026 — 82,146 monthly users19 September 2026 — 80,511 monthly users26 September 2026 — 75,477 monthly users29 August 202626 September 2026
15 measurements spanning 29 days, net -18,126. 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 72,758–96,322 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Sept 2026, 19:1875,477-5,034
19 Sept 2026, 16:3780,511-1,635
17 Sept 2026, 07:4182,146-2,431
15 Sept 2026, 09:3884,577-1,162
13 Sept 2026, 16:1985,739-1,424
12 Sept 2026, 00:3687,163-4,755
9 Sept 2026, 13:1791,918-966
6 Sept 2026, 02:5792,884+1,593
3 Sept 2026, 23:1991,291-1,839
2 Sept 2026, 15:4593,130-133
1 Sept 2026, 16:1393,263-237
31 Aug 2026, 14:4593,500+110
30 Aug 2026, 11:5893,390-213
29 Aug 2026, 11:2093,603no change
29 Aug 2026, 04:4593,603first 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“IzlaydiBot 🎵” (@OnashkaBot), 75,477 monthly users as measured 26 September 2026. Telegram Register, tgregister.com/channel/OnashkaBot.

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.