Continuamos no vip! 🛜✅

Channel
Lacerda - Double/Blaze
@lacerdafree
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,562subscribers
-126 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001553681619 |
|---|---|
| Type | Channel |
| Username | @lacerdafree |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/lacerdafree |
Topic
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 7 Oct 2026, 11:20 | 2,562 | -33 |
| 30 Sept 2026, 11:00 | 2,595 | -64 |
| 15 Sept 2026, 09:17 | 2,659 | +2 |
| 11 Sept 2026, 22:19 | 2,657 | -7 |
| 7 Sept 2026, 17:56 | 2,664 | -8 |
| 2 Sept 2026, 09:43 | 2,672 | +1 |
| 30 Aug 2026, 08:54 | 2,671 | +3 |
| 27 Aug 2026, 12:38 | 2,668 | -7 |
| 21 Aug 2026, 05:25 | 2,675 | -4 |
| 18 Aug 2026, 03:35 | 2,679 | +3 |
| 14 Aug 2026, 21:55 | 2,676 | -12 |
| 7 Aug 2026, 08:31 | 2,688 | no change |
| 7 Aug 2026, 08:25 | 2,688 | first reading |
Engagement
37 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 37 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
3 certeiros🚀
TÁ PAGOOOOO!!✅✅✅✅
ENTRADA CONFIRMADA! 🛜 🎯 Entrada: ⚫️ + ⚪️ 🛡️ Cobertura: até 1 martingale! 📊 Jogo: Double/Blaze 📲
2 sem gale!
TÁ PAGOOOOO!!✅✅✅✅
ENTRADA CONFIRMADA! 🛜 🎯 Entrada: ⚫️ + ⚪️ 🛡️ Cobertura: até 1 martingale! 📊 Jogo: Double/Blaze 📲
Bora lucrar🍀
TÁ PAGOOOOO!!✅✅✅✅
ENTRADA CONFIRMADA! 🛜 🎯 Entrada: 🔴 + ⚪️ 🛡️ Cobertura: até 1 martingale! 📊 Jogo: Double/Blaze 📲
🎯 Mais de 70% dos sinais no vip são assertivos sem necessidade de martingale. Tenha acesso aos nossos sinais e aproveite condições especiais para entrar no vip hoje! 📩 Chame no privado agora e descubra como fazer parte! @endersonlacerda
3 sem gale!
Showing the 12 most recent of 37 posts we hold for @lacerdafree. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Lacerda - Double/Blaze” (@lacerdafree), 2,562 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/lacerdafree.
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.