4 measurements spanning 32 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 21–23 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Sept 2026, 10:18
21
-1
31 Aug 2026, 23:39
22
-1
11 Aug 2026, 12:18
23
no change
8 Aug 2026, 10:45
23
first reading
Engagement
20 posts held, back to 28 February 2024 — 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 page 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 5 March 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
38 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 44.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
17
44.7%
❤
7
18.4%
⚡
4
10.5%
👏
4
10.5%
💯
2
5.26%
😁
2
5.26%
👍
1
2.63%
🤯
1
2.63%
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 14 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 38 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 28 February 2024 to 5 March 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
We have just officially burnt another 2% 🔥
Taking our total to 16%
https://bscscan.com/tx/0x2fe8811588dc8626dd1f02fb4ba5a340dd11d9225ce127396235c382ee0afca5
✅ Payment confirmed. Ticket: 23c867a733c74a7992f900d164b33cf5
- You will receive a message from BuyTech when the trending is confirmed (Pending Review)
-Time Stamp: March 04, 19:47 UTC
We just burnt another 2% of the supply
Total burnt now: 14% 🔥
If that isn’t bullish we don’t know what is 🐂
https://bscscan.com/tx/0x59361286500fa51eeee086c76edaa57c03d19f971a0a5acd3f52811912cad4ac
What's to come?
💥 Trending + Marketing coming weeks 🤫
🔥 More Burns to come, my Target is to burn 30%
🫱🏻🫲🏼 We will also look to have partnerships with other coins, so keep your eyes out for the ones we so
🐂 Our main utility will come but will take a while for it to be built, the other utility we have is COMMUNITY during the BULLRUN we expect to make hype an together we can do that
So for now bring in the chads y…
Again we have burnt another 2%
Taking it to 10.6% burnt now 🔥
We aren’t messing about BULLS now get me 10k fam an I will continue to burn
https://bscscan.com/tx/0xac643727027a27865f2dffaf87bbadeacfe3200e3a2735642f3d3cfd984db72f
It’s time to break that 8k resistance an work our way back to a new ATH!
We will be extending LP at 10k and burning another 2% of the supply which will take us to 5.4% burnt 🔥
Don’t miss the BULLRUN we are growing organically for now!
🐂🐂🐂
We have just went and burnt another 2% of the supply
Taking the total to 3.4% burnt 🔥
https://bscscan.com/tx/0x2a290f4ecb88917f01c0348f7f408f66b6bc9e0fbaa63261e0614c03eb361a01
Showing the 12 most recent of 20 posts we hold for @bullrunbscofficial. 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.
Mentions
Named by 1 registered channel — 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
6
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
6
vacant every time we have ever looked
@bullrunbscofficial named 6 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.
@aisoraen named in 1 post, 12 August 2026 – 12 August 2026
@babydogemoonglobal named in 1 post, 12 August 2026 – 12 August 2026
@babyshiba_bep20 named in 1 post, 12 August 2026 – 12 August 2026
@bitcoininu_official named in 1 post, 12 August 2026 – 12 August 2026
@mooky_bnb named in 1 post, 12 August 2026 – 12 August 2026
@nyny_official named in 1 post, 12 August 2026 – 12 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 September 2026 — this
entry's latest reading, not the date you are reading this.
“BullRun | OFFICIAL BSC Channel” (@bullrunbscofficial), 21 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/bullrunbscofficial.
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.