3 measurements spanning 8 days, net -2. 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 176–178 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Aug 2026, 21:18
176
-2
8 Aug 2026, 13:30
178
no change
8 Aug 2026, 10:04
178
first reading
Engagement
14 posts held, back to 4 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 1 pageof 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 14 posts for this entry, the most recent from 27 November 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
27 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 48.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
13
48.1%
👍
10
37.0%
🔥
4
14.8%
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 6 of the 14 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 27reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 4 September 2025 to 27 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🚀 BotBroad Update Notice!
We've made important improvements to the BotBroad platform:
📋 Recent Updates:
- New Login System: Moved from Telegram bot login to web interface with email/password authentication
- Enhanced Authentication: Updated API key security methods
- New Documentation: Complete API docs available at BotBroad Docs
- Improved Security: Better encryption for all API communications
- Bug Fixes: Vario…
⚠️ Fake Channel Alert!
Some users are copying our name, logo, and posts to mislead the community.
Please remember any channel not listed in @FlashComLists is NOT official
🚫 We do not collect payments from any other usernames or accounts.
✅ Our only trusted contact is @FlashComAssistant.
Stay safe and always verify before making any payment or sharing information. 💙
🚀 BotBroad Bots Dashboard Update
We're excited to announce new features in BotBroad Bot Dashboard!
What's New:
🔍 Search & Filters - Quickly find bots by name and filter by status (Online/Offline/Suspended)
🗑 Delete - Remove bots permanently from your dashboard
🤖 Add Bot Manually - Add bot manually now using your dashboar
📱 Enhanced Mobile UI - Better experience on all devices
⚡️ Improved Performance - Faster bot ma…
📢 Service Notice – BotBroadBot
🛠 @BotBroadBot is currently under maintenance
We’re performing scheduled maintenance to improve performance and stability.
✅ The BotBroad platform remain fully operational — you can continue managing your bots, broadcasts, and analytics as usual.
We appreciate your patience and understanding 💙
Stay tuned — the bot will be back online shortly!
📢 Important Update: BotBroad API Policy Launched!
Dear subscribers,
We are excited to announce the launch of the official BotBroad API Policy! 🎉
✅ Please read the new API policy carefully to ensure smooth usage and avoid any disruptions.
🔗 Read api policy
Thank you for being a part of the BotBroad community! 🚀
📢 BotBroad is Now Available on Web & App! 🚀
You can now use BotBroad directly from your browser or download our official Android APK for faster access and smoother performance! 📱💻
Stay connected, broadcast smarter, and reach your audience effortlessly with BotBroads ❤️
📢 BotBroad API v1.2.0 — Major System Update Released!
We’re thrilled to announce the release of BotBroad API v1.2.0, featuring a fully upgraded unified API engine, improved stability, and detailed broadcast insights.
🚀 What’s New
- New & Enhanced Request Types
- All requests are now handled through a single endpoint
More Supported types included:
multi — Register both a bot and user in one atomic request
reg…
🚀 Good News!
No more session issues 🎉
Your bot tokens are now securely stored in our database (encrypted). That means you only need to set your bot token once after logging in — no need to re-enter it every time.
Start using BotBroad by clicking here
✨ Extended Support : Telebot Creator
Now Optimized for Bots.Business + TeleBot Creator
You can now start adding TeleBot Creator bots to the broadcast system.
This update makes broadcasting more flexible and accessible for both platforms.
📖 Read the updated docs:
https://botbroad.iblogger.org/docs
❤5👍3🔥2
Showing the 12 most recent of 14 posts we hold for @BotBroad. 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.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Need Auto Ads + All Bots Broadcast System On BotBroad ?
Yes ❤️80%
Maybe 🤔0%
No some other features 🙁20%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 14 most recent posts we hold, published 4 September 2025 to 27 November 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank
Citation-graph rank — 371,572 of 1,584,420entries 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.
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 5 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.
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 16 August 2026 — this
entry's latest reading, not the date you are reading this.
“BotBroad - Telegram Bots Broadcasting System” (@BotBroad), 176 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/BotBroad.
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.