Telegram RegisterThe public register of Telegram
Telegram profile photo for Qo'shiq Bot | Muzikalar | Shazam

Bot

Qo'shiq Bot | Muzikalar | Shazam

@QoshiqBot

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

67,088monthly users

+3,756 since we began measuring on 7 August 2026

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

Register entry

Telegram ID5916666616
TypeBot
Username@QoshiqBot
First recorded11 August 2026
Last confirmed live28 October 2026
Measurements held43
Confirmed unchanged2 times, most recently 28 October 2026
On Telegramt.me/QoshiqBot

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

59,83873,52766,682.57 August 2026 — 63,332 monthly users8 August 2026 — 63,069 monthly users9 August 2026 — 62,655 monthly users10 August 2026 — 62,060 monthly users11 August 2026 — 62,060 monthly users12 August 2026 — 61,772 monthly users13 August 2026 — 61,607 monthly users14 August 2026 — 61,474 monthly users15 August 2026 — 61,327 monthly users17 August 2026 — 61,203 monthly users18 August 2026 — 60,944 monthly users19 August 2026 — 59,838 monthly users20 August 2026 — 60,622 monthly users22 August 2026 — 59,993 monthly users24 August 2026 — 60,532 monthly users25 August 2026 — 61,171 monthly users26 August 2026 — 61,458 monthly users27 August 2026 — 62,237 monthly users29 August 2026 — 62,593 monthly users30 August 2026 — 61,841 monthly users31 August 2026 — 63,645 monthly users1 September 2026 — 64,011 monthly users3 September 2026 — 64,296 monthly users6 September 2026 — 67,850 monthly users9 September 2026 — 69,816 monthly users11 September 2026 — 70,391 monthly users13 September 2026 — 70,426 monthly users15 September 2026 — 71,001 monthly users17 September 2026 — 71,367 monthly users26 September 2026 — 72,062 monthly users4 October 2026 — 73,527 monthly users9 October 2026 — 70,492 monthly users13 October 2026 — 69,827 monthly users14 October 2026 — 69,675 monthly users15 October 2026 — 69,393 monthly users17 October 2026 — 68,894 monthly users18 October 2026 — 68,491 monthly users20 October 2026 — 68,245 monthly users22 October 2026 — 67,673 monthly users23 October 2026 — 67,334 monthly users25 October 2026 — 66,906 monthly users26 October 2026 — 67,091 monthly users27 October 2026 — 67,088 monthly users67,0887 August 202627 October 2026
43 measurements spanning 81 days, net +3,756. 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 57,785–75,580 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 43
Measured (UTC)Monthly usersChange
27 Oct 2026, 00:5467,088-3
26 Oct 2026, 04:2067,091+185
25 Oct 2026, 04:2766,906-428
23 Oct 2026, 01:2067,334-339
22 Oct 2026, 00:4667,673-572
20 Oct 2026, 17:3868,245-246
18 Oct 2026, 17:2868,491-403
17 Oct 2026, 15:2968,894-499
15 Oct 2026, 19:2969,393-282
14 Oct 2026, 19:5669,675-152
13 Oct 2026, 07:5969,827-665
9 Oct 2026, 05:1770,492-3,035
4 Oct 2026, 17:1673,527+1,465
26 Sept 2026, 15:3672,062+695
17 Sept 2026, 13:4171,367+366
15 Sept 2026, 11:1771,001+575
13 Sept 2026, 16:3870,426+35
11 Sept 2026, 22:1670,391+575
9 Sept 2026, 10:1669,816+1,966
6 Sept 2026, 00:1767,850first 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 11 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 October 2026 — this entry's latest reading, not the date you are reading this.

“Qo'shiq Bot | Muzikalar | Shazam” (@QoshiqBot), 67,088 monthly users as measured 27 October 2026. Telegram Register, tgregister.com/channel/QoshiqBot.

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.