Telegram RegisterThe public register of Telegram
Telegram profile photo for Shazam_mbot Instagram musiqalar tiktok

Bot

Shazam_mbot Instagram musiqalar tiktok

@Shazam_mbot

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

220,695monthly users

-22,387 since we began measuring on 6 August 2026

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

Register entry

Telegram ID2001703752
TypeBot
Username@Shazam_mbot
First recorded6 August 2026
Last confirmed live6 November 2026
Measurements held58
Confirmed unchanged2 times, most recently 6 November 2026
On Telegramt.me/Shazam_mbot

Topic

Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 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

216,885258,834237,859.56 August 2026 — 243,082 monthly users6 August 2026 — 243,082 monthly users7 August 2026 — 243,308 monthly users8 August 2026 — 238,719 monthly users9 August 2026 — 239,440 monthly users10 August 2026 — 245,453 monthly users11 August 2026 — 245,446 monthly users12 August 2026 — 245,624 monthly users13 August 2026 — 246,229 monthly users15 August 2026 — 246,731 monthly users16 August 2026 — 247,360 monthly users17 August 2026 — 247,443 monthly users19 August 2026 — 247,401 monthly users20 August 2026 — 248,830 monthly users21 August 2026 — 244,829 monthly users23 August 2026 — 252,025 monthly users24 August 2026 — 253,686 monthly users26 August 2026 — 255,517 monthly users26 August 2026 — 256,414 monthly users28 August 2026 — 256,351 monthly users29 August 2026 — 257,151 monthly users30 August 2026 — 257,527 monthly users31 August 2026 — 258,834 monthly users1 September 2026 — 253,259 monthly users3 September 2026 — 254,425 monthly users4 September 2026 — 254,751 monthly users7 September 2026 — 255,002 monthly users10 September 2026 — 252,334 monthly users12 September 2026 — 252,568 monthly users14 September 2026 — 253,500 monthly users15 September 2026 — 254,108 monthly users18 September 2026 — 254,103 monthly users30 September 2026 — 245,801 monthly users5 October 2026 — 242,073 monthly users9 October 2026 — 237,335 monthly users13 October 2026 — 236,848 monthly users15 October 2026 — 236,249 monthly users15 October 2026 — 234,896 monthly users16 October 2026 — 233,437 monthly users18 October 2026 — 232,626 monthly users18 October 2026 — 232,499 monthly users19 October 2026 — 232,585 monthly users20 October 2026 — 231,596 monthly users22 October 2026 — 230,889 monthly users23 October 2026 — 229,913 monthly users24 October 2026 — 227,541 monthly users25 October 2026 — 225,324 monthly users26 October 2026 — 223,739 monthly users27 October 2026 — 217,833 monthly users28 October 2026 — 216,885 monthly users29 October 2026 — 219,126 monthly users30 October 2026 — 218,845 monthly users31 October 2026 — 218,888 monthly users1 November 2026 — 219,155 monthly users2 November 2026 — 220,993 monthly users3 November 2026 — 221,135 monthly users4 November 2026 — 220,735 monthly users5 November 2026 — 220,695 monthly users220,6956 August 20265 November 2026
58 measurements spanning 91 days, net -22,387. 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 210,593–265,126 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 58
Measured (UTC)Monthly usersChange
5 Nov 2026, 11:11220,695-40
4 Nov 2026, 12:18220,735-400
3 Nov 2026, 12:34221,135+142
2 Nov 2026, 08:57220,993+1,838
1 Nov 2026, 05:38219,155+267
31 Oct 2026, 05:01218,888+43
30 Oct 2026, 08:28218,845-281
29 Oct 2026, 08:26219,126+2,241
28 Oct 2026, 06:58216,885-948
27 Oct 2026, 07:29217,833-5,906
26 Oct 2026, 06:21223,739-1,585
25 Oct 2026, 07:21225,324-2,217
24 Oct 2026, 07:16227,541-2,372
23 Oct 2026, 06:10229,913-976
22 Oct 2026, 06:16230,889-707
20 Oct 2026, 23:26231,596-989
19 Oct 2026, 21:31232,585+86
18 Oct 2026, 23:00232,499-127
18 Oct 2026, 00:17232,626-811
16 Oct 2026, 23:44233,437first 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 33 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

Стандофф 2 читы, промокоди
@slandoff2 · 3
15 posts
Vn_shablon
@vn_shablomla01 · 1
11 posts
Ziyo reklama
@ziyo_rek · 1,669
6 posts
Husniddin
@husniddin0520 · 12
5 posts
Kanal
@mmmoshh · 2
5 posts
ZIYOTECH Dasturlash markazi
@ziyo_tech · 3,634
5 posts
𝐴𝑏𝑑𝑢𝑟𝑎ℎ𝑖𝑚𝑜𝑣
@abdurakhimoov_01 · 23
4 posts
شكرن🖤
@shkruon · 6
4 posts
[꙲꙰꯭❤️꯭]꙲꙰➧꙲꙰꯭🇧⃝꯭ᭂ꙲꙰꯭꙯𝐄꯭ᭂ꯭𝐆꯭ᭂ꯭𝐔꯭ᭂ𝐁꯭ᭂ꯭𝐎꯭ᭂ꯭𝐑꯭ᭂ𝐋꯭ᭂ𝐀꯭ᭂ꯭..𝐑꯭ᭂ꯭𝐈ᭂ꯭𝐌꯭➧꯭[꙲꙰꙲꙰꯭❤️꯭꙲꙰]꙲꙰꯭🕊️꯭
@xastaqalb05 · 2
4 posts
english
@english1881 · 1
3 posts
Moon
@moon_0517 · 4
3 posts
vital
@sorelle1moscow · 19
3 posts
꯭✨꯭🕋 ꯭̲̲̲̱̻̩̣̬̬͜͢᷼͡͝ ꯭𝐒꯭̅̅̄𝐇꯭̅̅̄𝐀꯭̅̅̄𝐗꯭̅̅̄𝐑꯭̅̅̄𝐈꯭̅̅̄𝐘꯭̅̅̄𝐎꯭̅̅̄𝐑꯭̅̅̄𖤓1꯭3꯭꯭3꯭1 🕋꯭꯭̲̲̲̱̻̩̣̬̬✨
@stonebakepro · 22
3 posts
Abu 🤍
@abu_shaxsi · 1
2 posts
꯭♕︎꯭꯭࿆⃝꦳꯭ꦿ𝐐꯭ᬼ.𝐎꯭ᬼ.𝐑꯭ᬼ.𝐀꯭ᬼ.𝐒꯭ᬼ.𝐎꯭ᬼ.𝐘꯭ᬼ.𝐀꯭ᬼ ꯭ࠫࠫ❀͜͡ ͜͡ꨄ︎
@Jovohir0709 · 1
2 posts
__SEVGI__VA__DÕSTLIK__
@baxronov20 · 1
1 post
꯭꯭𓆩꯭꯭🤍𓆪 𝐌🜧꯭꯭꯭꯭𝐀🜧꯭꯭꯭꯭𝐃🜧꯭꯭꯭꯭𝐈🜧꯭꯭꯭꯭꯭꯭𓆩꯭꯭🤍𓆪꯭꯭
@birdonangmanku · 22
1 post
Panohimsan
@Channel_Panohimsan · 3
1 post
Khilola’s_vlog🕊️
@fl_peoNy · 4
1 post
Ular baxtli
@ghfuyi · 2
1 post
Motivation MJ☠️🧠
@Motivation_MJ · 44
1 post
Yaqinlarim
@oalmagkspspow · 2
1 post
𝓶𝓸𝓸𝓷𝓼𝓱𝓲𝓷𝓮 ✨
@uletiiiii · 3
1 post

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

“Shazam_mbot Instagram musiqalar tiktok” (@Shazam_mbot), 220,695 monthly users as measured 5 November 2026. Telegram Register, tgregister.com/channel/Shazam_mbot.

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.