Telegram RegisterThe public register of Telegram
Telegram profile photo for Blaze BOT

Channel

Blaze BOT

@BLAZE_announcement

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

5,991subscribers

-133 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002068009560
TypeChannel
Username@BLAZE_announcement
Created4 February 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/BLAZE_announcement

Growth

5,9916,1246,057.57 August 2026 — 6,124 subscribers8 August 2026 — 6,120 subscribers11 August 2026 — 6,100 subscribers15 August 2026 — 6,082 subscribers17 August 2026 — 6,067 subscribers20 August 2026 — 6,054 subscribers24 August 2026 — 6,043 subscribers27 August 2026 — 6,031 subscribers29 August 2026 — 6,022 subscribers1 September 2026 — 6,003 subscribers6 September 2026 — 5,991 subscribers7 August 20266 September 2026
11 measurements spanning 30 days, net -133. 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 5,971–6,144 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 08:155,991-12
1 Sept 2026, 23:266,003-19
29 Aug 2026, 20:436,022-9
27 Aug 2026, 04:076,031-12
24 Aug 2026, 06:196,043-11
20 Aug 2026, 14:526,054-13
17 Aug 2026, 20:056,067-15
15 Aug 2026, 00:156,082-18
11 Aug 2026, 16:236,100-20
8 Aug 2026, 10:596,120-4
7 Aug 2026, 12:186,124first reading

Engagement

8 posts held, back to 4 February 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 9 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 8 posts for this entry, the most recent from 20 February 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1,754 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,00157.1%
🔥40523.1%
👍24714.1%
885.02%
🥰130.741%

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

Measured over the 8 most recent posts we hold, published 4 February 2024 to 20 February 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.

Recent posts

20 Feb 2024, 19:45 UTC≈17,800 views547 reactionsread 12 August 2026
Photo

☄️ BlazeBot update! We are happy to announce that we have updated BlazeBot and made it much faster and better. Also fixed all the bugs and errors! 🔥 So go ahead and trade and farm points! https://t.me/BLAZE_BLAST_BOT?start Type "/start" again for correct operation If you used the bot before the update and held test ETH on it, then don’t worry, soon all your ETH and farmed points will return to your balance Dupli

404👍79🔥64

13 Feb 2024, 18:44 UTC≈19,200 views720 reactionsread 12 August 2026

☄️ Global maintenance Thank you for taking part in the beta test and leaving your feedback, this will greatly help in improving the project. We are very grateful and appreciate your help ❤️ Having collected sufficient feedback for improvement, we are ready to adjust and make the bot better and faster, so within a day or two there will be technical work ❕ During the work the bot will be inactive. We made a backup

521👍11782

13 Feb 2024, 10:02 UTC≈16,700 views225 reactionsread 12 August 2026
Photo

☄️ BlazeBot on Blastscore! Great news: Join our Blastcore Campaign to get additional points in bot (which will be converted to ...🤫) bXP on Blastcore also will be valuable in the future blastscore.io/quest/blaze-bot Join, complete quests, and get rewarded!

🔥17738👍10

12 Feb 2024, 17:49 UTC≈8,890 views168 reactionsread 12 August 2026

☄️ How to use the bot? Brief guide: • Launch and fulfill the conditions • Click “👝Wallet” and “🚰Faucet Testnet $ETH”, wait • For trading you can use the following coin contracts: 0x290B7a542bb8642BE4469fa707B8a8F651CC958a 0xe38a3F0F647C72a6c9D948CBF40099Db56C175b1 Just send the address to the chat, or go to "🔥Buy tokens" • Go to “📕Active positions” and manage your positions Increase your volume and

🔥108👍2918🥰13

12 Feb 2024, 16:47 UTC≈6,020 views44 reactionsread 12 August 2026
Photo

☄️ BlazeBot is live! We're excited to announce the official launch of #BlazeBot! Buy, sell, snipe - earn money! It's easy and simple to do it in #BlazeBot 🔥 Let's go: t.me/BLAZE_BLAST_BOT Launch and use BlazeBot, become early user and be pleasantly rewarded with future drops (more info soon...) 🤫

🔥298👍7

8 Feb 2024, 18:19 UTC≈2,560 views24 reactionsread 12 August 2026

You should use Blaze Bot! And why? - Using our bot, you claim a drop from Blast itself (more about this a little later) - We have the lowest latency of any bot - The interface is no frills, and it is very simple and easy to use - Best prices, since Max Wynn bot uses a private aggregator contract - Stability and safety of work, as we use reliable and time-tested code Soon you will see for yourself...

🔥1365

5 Feb 2024, 20:51 UTC≈2,220 views26 reactionsread 12 August 2026

We are pleased to introduce you to #BlazeBot, a free Blast bot right in your Telegram The #BlazeBot is a DeFi upgrade on Blast. The fastest and most convenient way to easily trade and flip tokens on Blast with tons of features Get ready to get rich easily and simply! Soon...

🔥147👍5

Showing the 8 most recent of 8 posts we hold for @BLAZE_announcement. 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.

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

“Blaze BOT” (@BLAZE_announcement), 5,991 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/BLAZE_announcement.

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.