๐๐๐๐๐๐ ๐ ๐ ๐๐๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐ ๐๐ ๐๐๐ - ๐๐๐โน ๐๐๐ ๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐๐๐ ๐๐ ๐๐๐๐ ๐๐๐๐๐๐๐

Channel
๐๐๐๐ญ๐ ๐๐๐ฆ๐๐๐ง
@BlazeBasket
On this record: Topic ยท Growth ยท Engagement ยท Reactions ยท Posts ยท Cite this entry
7subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003423874188 |
|---|---|
| Type | Channel |
| Username | @BlazeBasket |
| Created | 29 December 2025 โ measured โ dated from the channelโs first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/BlazeBasket |
Topic
Software piracy โ 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 54% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 02:38 | 7 | +1 |
| 22 Aug 2026, 20:04 | 6 | +2 |
| 13 Aug 2026, 04:16 | 4 | no change |
| 7 Aug 2026, 19:01 | 4 | first reading |
Engagement
16 posts held, back to 29 December 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 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 16 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
7 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 71.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 5 | 71.4% | |
| โ | 1 | 14.3% | |
| ๐คฃ | 1 | 14.3% |
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 3 of the 16 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 7 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 16 most recent posts we hold, published 29 December 2025 to 18 July 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
๐ ๐๐๐ ๐๐ ๐'๐ฌ ๐๐ ๐๐๐๐ ๐๐๐๐๐ ๐๐ ๐๐๐ ๐๐๐๐ - โน๐๐ ๐๐๐+ ๐๐๐๐๐ ๐๐ ๐'๐ฌ ๐๐๐๐๐๐๐ ๐๐ ๐๐๐๐ ๐๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐ (๐๐๐ ๐๐๐๐๐๐๐๐) ๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐
CUSTOM WEBSITES MAKING AVAILABLE NICHE - BIRTHDAY/ANNIVERSARY ANY TYPE OF WISHES PRICE - 100โน ONLY
โค1
5 letter collectible username for sale @qnxra
3 ๐๐๐๐๐ฃ๐๐ฆ๐ง ๐ข๐ง๐ฃ ๐ฃ๐๐ก๐๐๐ฆ ๐๐ฉ๐๐๐๐๐๐๐ ๐ฃ๐ฅ๐๐๐ ๐ง๐ข ๐๐จ๐ฌ - โน79 all
40+ ACTIVE GC AVAILABLE BEST FOR SELLING
๐๐๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐ ๐๐ ๐๐๐ - โน5๐ ๐๐๐๐๐ ๐๐๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐๐๐ ๐ ๐๐ ๐๐๐๐๐๐๐
๐ท๐ถ๐ถ+ ๐แดแดสแดแด s ๐แดแด ๐แด แดษชสแดสสแด ๐สษชแดแด ๐แด ๐แดส - ๐ท๐ถ๐ถโน 79โน ๐แดแดแดแดแด ๐แดแดs (Including 3000+ methods f4ke payment apps and many more which can be used for selling)
๐๐ ๐ช๐ข๐ฅ๐๐ข๐จ๐ง ๐ฅ๐๐๐ ๐๐จ๐ก๐๐๐ ๐ฎ๐ฌ๐ฌ+ ๐ฃ๐ฅ๐๐๐ ๐ง๐ข ๐๐จ๐ฌ - โน๐ณ๐ฌ ๐๐ฆ๐ง ๐ฃ๐ข๐ฆ๐ง ๐๐ก๐ ๐๐ข ๐ฉ๐๐ฅ๐๐ ๐ฅ
๐ง๐ฅ๐๐๐๐ก๐ ๐ฅ๐๐๐๐ฆ ๐๐จ๐ก๐๐๐ ๐๐ฉ๐๐๐๐๐๐๐ (๐ฎ๐ฌ๐ฌ+ ๐ฅ๐๐๐๐ฆ) ๐ฃ๐ฅ๐๐๐ ๐ง๐ข ๐๐จ๐ฌ - โน๐ต๐ต ๐๐ฆ๐ง ๐ฃ๐ข๐ฆ๐ง ๐๐ก๐ ๐๐ข ๐ฉ๐๐ฅ๐๐
๐๐ง๐ ๐ฑ ๐ ๐ข๐๐๐๐ ๐ฃ๐ฅ๐๐๐ ๐ง๐ข ๐๐จ๐ฌ - โน๐ณ๐ฌ ๐ฅ๐จ๐ก ๐ฆ๐ ๐ข๐ข๐ง๐๐๐ฌ (๐๐๐๐๐๐ก๐ ๐ช๐๐๐๐ ๐ฆ๐๐ฅ๐๐๐ก ๐ฅ๐๐๐ข๐ฅ๐๐๐ก๐)
๐ ๐๐๐ ๐๐๐๐๐๐๐ ๐๐๐๐ โก ๐ ๐๐๐ ๐๐๐๐๐ ๐๐๐ โก ๐ ๐๐๐ ๐๐๐๐ โก ๐ ๐๐๐ ๐๐๐๐๐ โก ๐ ๐๐๐ ๐๐๐๐ ๐๐๐ โก ๐ ๐๐๐ ๐ ๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐ ๐๐๐๐๐ ๐๐๐ ๐๐๐ ๐ ๐๐๐๐๐๐๐ โก ๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐ โก ๐๐๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐ ๐๐๐๐ โก ๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐ ๐๐๐๐ ๐๐๐๐ ๐๐๐๐ ๐ฏ โก ๐๐๐ ๐๐๐๐ ๐๐๐ ๐๐๐๐๐ ๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐๐ ๐๐๐๐ ๐๐๐ ๐๐๐ ๐๐๐๐ (not soundbox) DM TO BUY - @QNXRA โน60 all
โ1
Showing the 12 most recent of 16 posts we hold for @BlazeBasket. 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 12 October 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐ญ๐ ๐๐๐ฆ๐๐๐งโ (@BlazeBasket), 7 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/BlazeBasket.
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.