National news — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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
63 measurements spanning 95 days, net -842. 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 18,650–19,744 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)
Subscribers
Change
9 Nov 2026, 08:44
18,776
-14
7 Nov 2026, 21:46
18,790
-6
6 Nov 2026, 16:16
18,796
-12
5 Nov 2026, 13:26
18,808
-4
4 Nov 2026, 11:18
18,812
-2
3 Nov 2026, 10:11
18,814
-5
2 Nov 2026, 10:36
18,819
-1
1 Nov 2026, 08:17
18,820
-6
31 Oct 2026, 05:27
18,826
-10
30 Oct 2026, 01:51
18,836
-9
29 Oct 2026, 01:17
18,845
-2
27 Oct 2026, 22:31
18,847
-4
26 Oct 2026, 19:40
18,851
-10
25 Oct 2026, 17:16
18,861
-6
24 Oct 2026, 19:50
18,867
-7
23 Oct 2026, 23:06
18,874
-11
23 Oct 2026, 00:31
18,885
-5
22 Oct 2026, 00:50
18,890
-6
20 Oct 2026, 19:48
18,896
-16
19 Oct 2026, 21:36
18,912
first reading
Engagement
22 posts held, back to 15 June 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 70 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 22 posts for this entry, the most recent from 28 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
33
Videos
4
Links
50
Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 24s
Average length
42s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
717 reactions across 21 posts, in 5 distinct kinds. The most used accounts for 37.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
269
37.5%
👍
204
28.5%
🔥
144
20.1%
👎
76
10.6%
🤩
24
3.35%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 22 of the 22 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 717 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 15 June 2023 to 28 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🚀 Claim 1 BILLION TOKENS on Muse AI
If you receive 1 billion tokens on Muse AI, you can use AI for free for longer and use them for research, shopping, tasks, and more. According to reports, the bonus tokens do not expire, so you don’t need to use them all immediately. ChatGPT, Gemini, and similar services may have limited free-token availability going forward, so this can potentially be used for a long time.
📲 Ste…
Hey guys, a friend of mine and their student team are building an electric go-kart from scratch for national competitions like GKDC! ⚡🏎️
They're raising funds to help cover parts, fabrication, and safety gear. Any support or share helps them get to the track:
👉 Support them here: http://m-lp.co/sanjaysu-6?utm_medium=whatsapp_status_poster&utm_source=app
Even small contributions or just forwarding this message …
🚫 India’s IT ministry banned Telegram for one week because some users shared leaked exam questions.
This punishes 150 million ordinary Telegram users in India — not the insiders who leaked the exam materials.
And the ban hasn't stopped anything. The leaks just moved to other apps.
🛡 We’ve done a lot to help fix the problem — even though its source is not Telegram.
Over the past few weeks, we removed hundreds of c…
📰 Telegram CEO Pavel Durov arrested at airport near Paris, French media reports
France's OFMIN, an agency tasked with preventing violence against minors, had issued an arrest warrant for Durov as the coordinating agency in a preliminary investigation into alleged offences including fraud, drug trafficking, cyberbullying, organized crime and promotion of terrorism, one of the sources close to the case told AFP.
Duro…
🔄 Update @IamUploadBot Beta V3 🔖
✅ Duration not showing on Videos
✅ Auto Thumbnail added on Videos
✅ m3u8 Files Uploading
✅ Google Drive Links Supporting
✅ Queue System Improved
✅ Better Speed
✅ Some minor Bugs
😄 As I've mentioned this is an initial build so bugs may be found.In my tests i cannot find anything so if you find anything wrong please let me know in
@Viruzs | @InFoTelGroup
🔥28👍21❤8👎3
Signed ᴠɪʀᴜᴢZ 🔥⌚🔥📅
Showing the 12 most recent of 22 posts we hold for @TGBotsz. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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.
Mentions
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
Dead references
3
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
3
vacant every time we have ever looked
@TGBotsz named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@premiumgiveaways_bg named in 6 posts, 8 August 2026 – 16 August 2026
@botdatabaseelbot named in 5 posts, 8 August 2026 – 18 August 2026
@elsupport named in 5 posts, 8 August 2026 – 18 August 2026
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“TG Bots Updates” (@TGBotsz), 18,776 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/TGBotsz.
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.