Telegram RegisterThe public register of Telegram
Telegram profile photo for Video Yukla Bot | Shazam

Bot

Video Yukla Bot | Shazam

@VideoYuklaBot

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

78,326monthly users

-15,414 since we began measuring on 6 August 2026

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

Register entry

Telegram ID5837888379
TypeBot
Username@VideoYuklaBot
First recorded10 August 2026
Last confirmed live10 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/VideoYuklaBot

Topic

Other / unclassifiable — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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

78,326118,25698,2916 August 2026 — 93,740 monthly users7 August 2026 — 93,419 monthly users8 August 2026 — 93,447 monthly users9 August 2026 — 93,346 monthly users10 August 2026 — 93,006 monthly users10 August 2026 — 93,006 monthly users12 August 2026 — 96,153 monthly users13 August 2026 — 97,257 monthly users14 August 2026 — 97,881 monthly users15 August 2026 — 98,532 monthly users17 August 2026 — 97,307 monthly users18 August 2026 — 97,188 monthly users19 August 2026 — 97,201 monthly users20 August 2026 — 97,182 monthly users21 August 2026 — 97,136 monthly users22 August 2026 — 96,857 monthly users24 August 2026 — 92,047 monthly users25 August 2026 — 91,061 monthly users26 August 2026 — 90,516 monthly users27 August 2026 — 90,671 monthly users29 August 2026 — 89,795 monthly users30 August 2026 — 88,837 monthly users31 August 2026 — 87,240 monthly users1 September 2026 — 86,257 monthly users2 September 2026 — 84,814 monthly users4 September 2026 — 85,336 monthly users6 September 2026 — 85,799 monthly users9 September 2026 — 95,030 monthly users12 September 2026 — 94,184 monthly users13 September 2026 — 97,720 monthly users15 September 2026 — 103,622 monthly users17 September 2026 — 105,195 monthly users25 September 2026 — 108,167 monthly users4 October 2026 — 118,256 monthly users8 October 2026 — 116,512 monthly users13 October 2026 — 111,219 monthly users14 October 2026 — 109,082 monthly users16 October 2026 — 102,447 monthly users19 October 2026 — 98,733 monthly users20 October 2026 — 97,138 monthly users22 October 2026 — 96,689 monthly users24 October 2026 — 95,785 monthly users25 October 2026 — 95,582 monthly users26 October 2026 — 95,339 monthly users27 October 2026 — 94,533 monthly users28 October 2026 — 90,594 monthly users29 October 2026 — 90,004 monthly users31 October 2026 — 88,714 monthly users1 November 2026 — 85,046 monthly users2 November 2026 — 84,231 monthly users3 November 2026 — 82,068 monthly users4 November 2026 — 80,888 monthly users5 November 2026 — 82,893 monthly users7 November 2026 — 82,176 monthly users8 November 2026 — 81,682 monthly users10 November 2026 — 78,326 monthly users6 August 202610 November 2026
56 measurements spanning 96 days, net -15,414. 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,337–124,246 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 56
Measured (UTC)Monthly usersChange
10 Nov 2026, 00:5878,326-3,356
8 Nov 2026, 15:4881,682-494
7 Nov 2026, 08:1882,176-717
5 Nov 2026, 11:5182,893+2,005
4 Nov 2026, 10:3180,888-1,180
3 Nov 2026, 08:3682,068-2,163
2 Nov 2026, 08:5584,231-815
1 Nov 2026, 08:5685,046-3,668
31 Oct 2026, 06:3188,714-1,290
29 Oct 2026, 04:4890,004-590
28 Oct 2026, 05:4990,594-3,939
27 Oct 2026, 05:3794,533-806
26 Oct 2026, 02:3795,339-243
25 Oct 2026, 04:2795,582-203
24 Oct 2026, 01:0695,785-904
22 Oct 2026, 22:0896,689-449
20 Oct 2026, 16:5597,138-1,595
19 Oct 2026, 17:2898,733-3,714
16 Oct 2026, 18:06102,447-6,635
14 Oct 2026, 16:39109,082first 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 66 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 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Video Yukla Bot | Shazam” (@VideoYuklaBot), 78,326 monthly users as measured 10 November 2026. Telegram Register, tgregister.com/channel/VideoYuklaBot.

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.