Technology — 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 48% 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
53 measurements spanning 83 days, net -982. 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,830–20,106 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 53
Measured (UTC)
Subscribers
Change
29 Oct 2026, 22:29
18,977
-14
28 Oct 2026, 21:50
18,991
-19
27 Oct 2026, 19:41
19,010
-18
26 Oct 2026, 17:57
19,028
-15
25 Oct 2026, 16:30
19,043
-9
24 Oct 2026, 17:14
19,052
-11
23 Oct 2026, 14:58
19,063
-18
22 Oct 2026, 18:10
19,081
-10
21 Oct 2026, 11:37
19,091
-17
20 Oct 2026, 11:56
19,108
-22
19 Oct 2026, 09:17
19,130
-17
18 Oct 2026, 09:06
19,147
-19
17 Oct 2026, 11:46
19,166
-28
16 Oct 2026, 14:56
19,194
-4
15 Oct 2026, 17:16
19,198
-4
14 Oct 2026, 20:11
19,202
-18
13 Oct 2026, 13:56
19,220
-32
9 Oct 2026, 15:59
19,252
-30
5 Oct 2026, 05:36
19,282
-8
28 Sept 2026, 13:00
19,290
first reading
Engagement
20 posts held, back to 3 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 56 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 20 posts for this entry, the most recent from 17 February 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
956 reactions across 20 posts, in 27 distinct kinds. The most used accounts for 29.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
279
29.2%
❤🔥
75
7.85%
🤣
67
7.01%
💩
62
6.49%
🖕
60
6.28%
😭
56
5.86%
👍
55
5.75%
👏
44
4.60%
🥰
39
4.08%
🤡
38
3.97%
🔥
34
3.56%
🤮
33
3.45%
👎
31
3.24%
🍌
22
2.30%
🤬
16
1.67%
😁
8
0.837%
⚡
5
0.523%
🐳
5
0.523%
😢
5
0.523%
😱
5
0.523%
7 further kinds
17
1.78%
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 20 of the 20 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 956 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 3 September 2025 to 17 February 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.
🚨 BIG UPDATE. HUGE. 🚨
Listen up. The Restricted Content Saver Bots? They’ve been updated. Completely refreshed. Stronger than ever.
Every bug — gone.
Every issue — fixed.
Performance — incredible. Maybe the best you’ve ever seen. People are saying it.
The Free Bot? It’s LIVE. Working beautifully. Fast. Reliable. Tremendous.
The Premium Bot subscriptions? Back and selling again. Strong support. Smart people joinin…
Fixed some of the issues, If some features aren't working just dont use them for now. also Clear all settings using the Reset All Settings Button in /settings.
I'm currently traveling, you guys will have to wait 2-3 days then only i can fix the remaining issue
Don't worry, just dm me after 3 days and I'll extend your subscription for 1 week more
If your bot stops responding, then
1. Go to main bot
2. Use /removebot to remove bot
3. Re add your bot using /setbot
& It will be fixed.
Do note that, this update was made in hurry, so it will take time to fix bugs. So have patience.
All Bots Are Fixed & Live Now !!
Free Restricted Content Saver Bot:
@Free_RDownloader_Bot
Premium Restricted Content Saver Bots:
@Premium_Downloader1_Bot
@Premium_Downloader2_Bot
Use Your Assigned Bots.
Note: To Avoid Bans By Telegram.
1. Downloaded Messages Will Be Sent To Your Saved Messages Unless Forwarding Is Set.
2. You'll Need To Set Your Custom Bot Using /setbot Command.
You have created a malicious bot that was banned on Telegram. Please note that creating abusive bots (for example, bots for spamming and interfering with communication in groups) may lead to your account being terminated.
You have been banned from creating new bots for a month.
And here's an offer you can't refuse: Once the month is over, you can either play nice and build useful bots (or no bots at all) — or be bl…
Telegram is banning Restricted Content Saver Bots, 2 of our Bots got banned again. We are looking for an alternative, don't worry we'll provide Fix for this issue/New Bot. Just wait patiently.
Estimated Time For Fix: 2-3 Days Max
All Bots Fixed & Live Now, Had Some Issue With AWS Database
❤21👏13🖕7🍌6🥰5
Showing the 12 most recent of 20 posts we hold for @JarvisBotz. 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.
Handles this channel named that no longer answer
Dead references
4
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
4
vacant every time we have ever looked
@JarvisBotz named 4 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.
@save_restrictedcontents_bot named in 28 posts, 8 August 2026 – 15 August 2026
@content_saverpremium_bot named in 6 posts, 8 August 2026 – 15 August 2026
@save_restrictedcontents_ named in 6 posts, 8 August 2026 – 15 August 2026
@content_saver_free_bot named in 2 posts, 8 August 2026 – 9 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 29 October 2026 — this
entry's latest reading, not the date you are reading this.
“JarvisBotz ⚡️” (@JarvisBotz), 18,977 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/JarvisBotz.
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.