Новая игра которая потенциально раздаст! ⚡️ A new game that will give away money! ⚡️ http://t.me/token1win_bot/start?startapp=refId912309763

Channel
Blum Invite || Блум инвайт 🚀
@blum_invites24
On this record: Growth · Engagement · Posts · Citations · Cite this entry
27subscribers
-2 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 | -1002066380002 |
|---|---|
| Type | Channel |
| Username | @blum_invites24 |
| Created | 2 February 2024 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/blum_invites24 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 03:38 | 27 | -1 |
| 16 Aug 2026, 06:08 | 28 | -1 |
| 11 Aug 2026, 05:16 | 29 | no change |
| 7 Aug 2026, 12:43 | 29 | first reading |
Engagement
11 posts held, back to 2 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 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 11 posts for this entry, the most recent from 5 July 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Active invite! || Активный инвайт! ✔️ 200 left || Осталось 200 мест! ⚡️ t.me/BlumCryptoBot/app?startapp=ref_nJf2EMPg7V
Active invite! ✔️ http://t.me/BlumCryptoBot/app?startapp=ref_SuuSZdI49l
New tasks! ⚡️ Available 1 week ⚠️
Active invite! ✔️ t.me/BlumCryptoBot/app?startapp=ref_nJf2EMPg7V
Active invite! ✅ http://t.me/BlumCryptoBot/app?startapp=ref_lvnkyBZNjR
🔥 Snapshot has been taken! Share in the comments how many points you have received.
If you have used the code, please write about it in the comments 😁
Active BounceBit Early Access Codes:
Current codes for access to BounceBit, if there is a demand, the codes will be updated with new ones over time: https://bouncebit.io?code=HK3CX https://bouncebit.io?code=5GNJ6 https://bouncebit.io?code=64IO3 https://bouncebit.io?code=H7A0N https://bouncebit.io?code=QVFFF https://bouncebit.io?code=C0R2X
Channel created
Showing the 11 most recent of 11 posts we hold for @blum_invites24. 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
Names
Channels on the register whose handles appear in this channel's posts.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Blum Invite || Блум инвайт 🚀” (@blum_invites24), 27 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/blum_invites24.
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.