Telegram RegisterThe public register of Telegram
Telegram profile photo for Mad Bots | News, updates, etc...

Channel

Mad Bots | News, updates, etc...

@mad_bots

2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Domains linked from posts · Cite this entry

555,427subscribers

-9,874 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001450453299
TypeChannel
Usernames@mad_bots @madbots
Description🇬🇧 English | 🇷🇺 Русский Our Army of Bots | Наша армия ботов: @AximoBot @download_it_bot @AuxioBot @mad_ai_bot @ChatZillaBot @voice_remover_bot @WTSong_bot @NudesRemoverBot @ChatPolyglotBot @InstantMediaBot @HypemeterBot Official group: @madbots_talk
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live22 August 2026
Measurements held30
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/mad_bots

Topic

Technology — 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 why it has no browse page of its own yet.

Growth

555,427565,301560,3647 August 2026 — 565,301 subscribers7 August 2026 — 565,301 subscribers7 August 2026 — 564,947 subscribers8 August 2026 — 564,116 subscribers9 August 2026 — 563,787 subscribers9 August 2026 — 563,752 subscribers9 August 2026 — 563,538 subscribers10 August 2026 — 563,096 subscribers10 August 2026 — 562,861 subscribers11 August 2026 — 562,519 subscribers11 August 2026 — 562,185 subscribers12 August 2026 — 561,911 subscribers12 August 2026 — 561,646 subscribers13 August 2026 — 561,353 subscribers13 August 2026 — 561,123 subscribers14 August 2026 — 560,609 subscribers15 August 2026 — 560,395 subscribers16 August 2026 — 559,741 subscribers16 August 2026 — 559,484 subscribers17 August 2026 — 559,029 subscribers17 August 2026 — 558,810 subscribers18 August 2026 — 558,526 subscribers18 August 2026 — 558,362 subscribers19 August 2026 — 557,965 subscribers19 August 2026 — 557,847 subscribers20 August 2026 — 557,342 subscribers20 August 2026 — 557,009 subscribers21 August 2026 — 556,328 subscribers22 August 2026 — 555,864 subscribers22 August 2026 — 555,427 subscribers7 August 202622 August 2026
30 measurements spanning 16 days, net -9,874. 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 553,946–566,782 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
22 Aug 2026, 19:55555,427-437
22 Aug 2026, 06:05555,864-464
21 Aug 2026, 13:23556,328-681
20 Aug 2026, 18:13557,009-333
20 Aug 2026, 13:14557,342-505
19 Aug 2026, 15:34557,847-118
19 Aug 2026, 14:37557,965-397
18 Aug 2026, 17:26558,362-164
18 Aug 2026, 12:35558,526-284
17 Aug 2026, 20:27558,810-219
17 Aug 2026, 13:45559,029-455
16 Aug 2026, 17:14559,484-257
16 Aug 2026, 06:17559,741-654
15 Aug 2026, 02:38560,395-214
14 Aug 2026, 14:47560,609-514
13 Aug 2026, 16:07561,123-230
13 Aug 2026, 07:24561,353-293
12 Aug 2026, 16:38561,646-265
12 Aug 2026, 05:16561,911-274
11 Aug 2026, 17:27562,185first reading

Engagement

21 posts held, back to 24 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.46%
avg views ÷ 555,427 subscribers
Avg views / post
30,300
3 posts measured
Reaction rate
0.218%
reactions ÷ views · ER floor
Posts in window
3
of 21 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 August 2026
Posts held21 (24 February 202620 August 2026)
Views total90,900
Reactions total198
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 22:21 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
1
Links
46

Lifetime counters from Telegram’s own channel header, read 22 August 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.

Reaction mix

2,313 reactions across 21 posts, in 20 distinct kinds. The most used accounts for 61.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,43261.9%
👍39116.9%
🔥1928.30%
❤‍🔥783.37%
👌421.82%
👎361.56%
271.17%
🤣200.865%
👏180.778%
🆒130.562%
😐110.476%
🤬100.432%
🥴90.389%
🎉60.259%
🏆60.259%
😍60.259%
🤪60.259%
🥰60.259%
🤔30.13%
😱10.043%

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 21 of the 21 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 2,313reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 24 February 2026 to 20 August 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.

Recent posts

20 Aug 2026, 17:07 UTC≈13,000 views45 reactionsread 22 August 2026

🎉 Good news, everyone! Especially for @AximoBot users! Hey again, everyone! We're still hard at work moving Aximo over to the new logic, we seriously underestimated the amount of work involved, so we'll fully wrap it up closer to the first half of September. In the process we lost some things, gained some others. Fair warning: we're reworking a lot, plans, prices and the feature list, so while you still can, grab it

26👍14🔥4🥰1

5 Aug 2026, 23:37 UTC≈35,800 views70 reactionsread 22 August 2026

✍️ Good news, everyone! Especially for @download_it_bot users! The system's been shaky for a few days, we looked into it and got a bit shocked: roughly 0.5% of users were generating around 20% of the total load. So we'll soon be tightening some limits a bit and adding automatic checks, since the other 99.5% were suffering because of it and that needed fixing. Now for your favorite segment: improvements and new featu

39🔥18🆒7❤‍🔥4👌2

29 Jul 2026, 00:08 UTC≈42,100 views83 reactionsread 22 August 2026

🔔 Good news, everyone! Hey everyone, we're up to our necks working on @AximoBot, but we haven't forgotten about the other bots either. We've got plenty to show off, so let's go. Let's start with @download_it_bot: — Spun up a separate pool of Russian proxies, delivery from VK, Yandex and Odnoklassniki got noticeably more stable. — Added support for streams and podcasts, including Twitter Spaces, important note: only

53🔥16👌7👍6👎1

22 Jul 2026, 00:22 UTC≈47,100 views71 reactionsread 22 August 2026

🔵 Good news, everyone! Especially for @AximoBot users! We haven't written about Aximo for almost two months, but don't think we were sitting idle. All this time we were preparing to migrate your favorite forwarder bot to the new system, but got buried, since it turned out to be quite tricky. Part of the system (the monitoring in particular) is already migrated, all that's left is to switch everything to the same del

47👍15🥴4🤔3🤣2

14 Jul 2026, 22:22 UTC≈54,500 views87 reactionsread 22 August 2026

🎉 Good news, everyone! Especially for @download_it_bot users! Hey again. We keep improving, optimizing and fixing bugs. And given the load and the number of requests, there's plenty of them. Anyway, let's get to the list of what's new and not only. Brace yourselves, there's a lot: — We moved the bot to the new system, but not your file history. So we had to run a migration, it took us almost two weeks, and we moved

46👍23🔥9👏8😱1

30 Jun 2026, 23:51 UTC≈64,500 views95 reactionsread 22 August 2026

💥 Good news, everyone! Especially for @download_it_bot users! Hey, it's us again. The bot might be a bit shaky these past few days since we're very actively working on optimization, improvements and just polishing the little things. Plus the more we work on speed, the more links you throw at it for processing and everything starts lagging again. That's life. Now, what's new and not so new: — Files with non-Latin na

49👍27🔥10👎6👌3

21 Jun 2026, 23:04 UTC≈67,500 views92 reactionsread 22 August 2026

🔥 Good news, everyone! Especially for @download_it_bot users! Hey, we keep polishing the bot, so here's a fresh batch of fixes and improvements: — Fixed the biggest pain point: uploading heavy files to Telegram. It took some effort, but now even a couple-gig file is no problem for us. — Added smart control of link lifetime and requesting fresh formats. Otherwise you'd sometimes hit an error when trying to download

51👍26🤬7🏆6❤‍🔥2

15 Jun 2026, 00:28 UTC≈67,600 views84 reactionsread 22 August 2026

💻 Good news, everyone! Especially for @download_it_bot users! Hey again, everyone! We're actively finishing up the bots, so there might be occasional glitches. Now let's continue with the news: — Oh, and we almost forgot: after moving to the new system we reset everyone's trial usage, so you can try our premium features again. — For YouTube, added the option to download the full video description and subtitles in y

46👍21🔥11👌5👎1

11 Jun 2026, 00:25 UTC≈71,600 views100 reactionsread 22 August 2026

☄️ Good news, everyone! Especially for @download_it_bot users! It wasn't easy, but we did it. We've fully migrated @download_it_bot to the new system. This was long overdue since we'd hit the limits of the old architecture. There are a ton of changes, too many for one post. Let's start with plans: — Important: the migration is still ongoing, so issues are possible. To be fair, we've added a free week of premium for

61🔥16👌12👍83

1 Jun 2026, 00:32 UTC≈95,300 views130 reactionsread 22 August 2026

📺 Good news, everyone! Hey, not a lot of news today, but it covers three bots at once. @ChatzillaBot Added a mega cool feature: join request management for groups. The scheme is pretty standard: enable join moderation and then either auto-approve or moderate manually. Feature list: — Auto-rejection rules: RTL characters in name or bio (a classic spam marker), accounts without a public @username. — Stop words in nam

88👍21🔥12🥰54

20 May 2026, 18:58 UTC≈112,000 views160 reactionsread 22 August 2026

🚀 Good news, everyone! Hey, long time no see, naturally because we've been crazy busy. As part of the migration to the new architecture, we had a huge task: move everything to a new database, ideally without anyone noticing. Which is exactly what we did over the past few days. We had to take @download_it_bot offline for about an hour and pause forwarding in @AximoBot for a couple hours, but the system caught up quic

103👍25🔥188👌6

11 May 2026, 00:23 UTC≈116,000 views155 reactionsread 22 August 2026

🫦 Good news, everyone! Especially for @NudesRemoverBot users! User and chat counts keep growing, and with that the load, which is logical. But there are downsides. Over the past couple weeks the system slowed down several times, and once the queue grew to 1000+ items, so some messages got checked only an hour later. Obviously unacceptable. We sat down, thought hard, scratched our heads and optimized everything, rew

75👍36👎24😐11🔥9

Showing the 12 most recent of 21 posts we hold for @mad_bots. 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.

Citation-graph rank

Citation-graph rank — 1,419,086 of 1,584,142entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

Domains linked from posts

5 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

pin.it1 post · 21 June 2026 – 21 June 2026 · example post
share.google1 post · 14 July 2026 – 14 July 2026 · example postNot linked — blocklisted domain
t.co1 post · 14 July 2026 – 14 July 2026 · example post
vk.com1 post · 18 March 2026 – 18 March 2026 · example post
vk.ru1 post · 18 March 2026 – 18 March 2026 · example post

1 of 5 shown as text only, not a link. The exact host, not merely a domain it shares a registrable root with, matches a threat-intelligence blocklist this register already checks elsewhere (see methodology) — the link still appearing in a post is still a measured fact and is still shown, but no anchor is rendered here, so no click and no link equity passes to it from this page.

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

“Mad Bots | News, updates, etc...” (@mad_bots), 555,427 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/mad_bots.

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.