31 Dec 2023, 14:11 UTCviews —
Messages in this channel will no longer be automatically deleted
Channel
Fortune HACK!
@reidablazedoublevip
On this record: Growth · Engagement · Posts · Cite this entry
350subscribers
-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 | -1001789173501 |
|---|---|
| Type | Channel |
| Username | @reidablazedoublevip |
| Created | Between 1 December 2021 and 30 August 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/reidablazedoublevip |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 23:26 | 350 | -1 |
| 15 Aug 2026, 18:37 | 351 | -1 |
| 7 Aug 2026, 16:18 | 352 | -1 |
| 7 Aug 2026, 06:17 | 353 | first reading |
Engagement
20 posts held, back to 30 August 2022 — 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 20 posts for this entry, the most recent from 31 December 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
3 Dec 2023, 23:52 UTCviews —
Messages in this channel will be automatically deleted after 1 day
2 Nov 2022, 00:32 UTCviews —
Messages in this channel will be automatically deleted after 1 month
30 Aug 2022, 07:19 UTCviews —
Fortune HACK! pinned Deleted message
30 Aug 2022, 02:52 UTC214 viewsread 7 August 2026
🟢 DOUBLE CONFIRMADO 🟢 🔔 Entrar no ⚫️ AGORA! 🔔 ⚔️ Entrar após o nº 1 ⚠️ Aplicar no Máximo ²Gales 🛡️ Proteção no ⚪️ [opcional] 🖥 ACESSAR DOUBLE (https://wun.bet/double)
30 Aug 2022, 02:50 UTC173 viewsread 7 August 2026
✅ ENTRAMOS NO (🟡) 🤑 O RESULTADO FOI = 🟡
30 Aug 2022, 02:50 UTC179 viewsread 7 August 2026
🚦 Placar Parcial ✅ = 420 ⛔️ = 61 ⚪ = 76 🎯 89.05% de acerto
30 Aug 2022, 02:49 UTC157 viewsread 7 August 2026
🟢 DOUBLE CONFIRMADO 🟢 🔔 Entrar no 🟡 AGORA! 🔔 ⚔️ Entrar após o nº 11 ⚠️ Aplicar no Máximo ²Gales 🛡️ Proteção no ⚪️ [opcional] 🖥 ACESSAR DOUBLE (https://wun.bet/double)
30 Aug 2022, 02:48 UTC140 viewsread 7 August 2026
✅ ENTRAMOS NO (⚫️) 🤑 O RESULTADO FOI = ⚫️
30 Aug 2022, 02:48 UTC156 viewsread 7 August 2026
🚦 Placar Parcial ✅ = 419 ⛔️ = 61 ⚪ = 76 🎯 89.03% de acerto
30 Aug 2022, 02:48 UTC104 viewsread 7 August 2026
Entrar gale 1
30 Aug 2022, 02:47 UTC104 viewsread 7 August 2026
🟢 DOUBLE CONFIRMADO 🟢 🔔 Entrar no ⚫️ AGORA! 🔔 ⚔️ Entrar após o nº 2 ⚠️ Aplicar no Máximo ²Gales 🛡️ Proteção no ⚪️ [opcional] 🖥 ACESSAR DOUBLE (https://wun.bet/double)
Showing the 12 most recent of 20 posts we hold for @reidablazedoublevip. 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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Fortune HACK!” (@reidablazedoublevip), 350 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/reidablazedoublevip.
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.