Channel
@zerolossdelay
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Polls · Cite this entry
998subscribers
+160 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003857624271 |
|---|---|
| Type | Channel |
| Username | @zerolossdelay |
| Created | Between 1 February 2026 and 18 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/zerolossdelay |
Gambling & betting — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 06:39 | 998 | +36 |
| 10 Sept 2026, 19:57 | 962 | +69 |
| 2 Sept 2026, 00:04 | 893 | +28 |
| 25 Aug 2026, 02:37 | 865 | -13 |
| 16 Aug 2026, 22:23 | 878 | +41 |
| 8 Aug 2026, 14:52 | 837 | -1 |
| 8 Aug 2026, 01:21 | 838 | no change |
| 7 Aug 2026, 18:22 | 838 | first reading |
20 posts held, back to 18 July 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 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Lucas aproveitou e lucrou com a nossa transmissão de Delay!! 🚀🚀 Parabéns Lucas, lucrando MUITO com as nossas lives de Delay - totalmente sem riscos! Com o Delay, você lucra sem riscos e sem precisar de Proteção! 🚀🚀 Chame @davizeroloss
R$1.330 DE LUCRO COM DELAY - 3ª ENTRADA!!! ✅✅
R$516 DE LUCRO COM DELAY - 2ª ENTRADA!!! ✅✅
R$455 DE LUCRO COM DELAY - 1ª ENTRADA!!! ✅✅
Photo, posted without a caption
BOA NOITE PESSOAL!!! 🚀🚀🚀
ESTAMOS AO VIVO!! 🚀🚀🚀 Já lucramos na primeira narração de hoje, às 08:00, e agora seguimos AO VIVO em mais uma transmissão exclusiva! 🏟️💸 Quem entrou pro Delay está colocando muita grana no bolso!!! 🤑🤑🤑 Aproveitamos o Atraso das casas de apostas e conseguimos operações com Lucro Garantido sem riscos! 🚀 Chame @davizeroloss
BOA TARDE PESSOAL!!! 🚀🚀🚀
Photo, posted without a caption
Me chama 👉🏻 @davizeroloss
No vídeo acima, você viu exatamente como lucramos: 1️⃣ O Gol acontece no campo. 2️⃣ Nossa transmissão é mais rápida que a da casa de apostas. 3️⃣ Aproveitamos esse "atraso" (delay) da casa e fazemos a entrada. 4️⃣ A casa fecha o mercado depois que já garantimos a aposta. Resultado? Lucro no bolso antes mesmo da odd atualizar. 💸
Não é sorte, é estrutura. Temos uma equipe de 7 Analistas monitorando jogos do mundo todo para te entregar tudo mastigado.
Showing the 12 most recent of 20 posts we hold for @zerolossdelay. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Você sabe como funciona o Delay esportivo?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 18 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“ZERO LOSS DELAY” (@zerolossdelay), 998 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/zerolossdelay.
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.