Channel
@chuvadepremio
On this record: Topic · Growth · Engagement · Posts · Cite this entry
13,565subscribers
-932 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001580010444 |
|---|---|
| Type | Channel |
| Username | @chuvadepremio |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 56 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/chuvadepremio |
Marketing & affiliate — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Oct 2026, 15:05 | 13,565 | -11 |
| 29 Oct 2026, 17:14 | 13,576 | -7 |
| 28 Oct 2026, 17:00 | 13,583 | -11 |
| 27 Oct 2026, 17:10 | 13,594 | -5 |
| 26 Oct 2026, 17:11 | 13,599 | -10 |
| 25 Oct 2026, 18:21 | 13,609 | -12 |
| 24 Oct 2026, 15:54 | 13,621 | -4 |
| 23 Oct 2026, 17:26 | 13,625 | -10 |
| 22 Oct 2026, 19:26 | 13,635 | -6 |
| 21 Oct 2026, 14:57 | 13,641 | -15 |
| 20 Oct 2026, 11:39 | 13,656 | -11 |
| 19 Oct 2026, 12:26 | 13,667 | -3 |
| 18 Oct 2026, 10:20 | 13,670 | -12 |
| 17 Oct 2026, 08:36 | 13,682 | -20 |
| 16 Oct 2026, 08:27 | 13,702 | -3 |
| 15 Oct 2026, 09:39 | 13,705 | -9 |
| 14 Oct 2026, 12:17 | 13,714 | -22 |
| 13 Oct 2026, 00:10 | 13,736 | -37 |
| 8 Oct 2026, 17:58 | 13,773 | -64 |
| 4 Oct 2026, 06:54 | 13,837 | first reading |
2 posts held, back to 27 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 27 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 2 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
💰📱 QUER FAZER UMA RENDA EXTRA USANDO APENAS O CELULAR? A Hub disponibiliza tarefas para pessoas ajudarem no treinamento de Inteligência Artificial 🤖 E o melhor: 🔥 VOCÊ NÃO PRECISA GASTAR NEM R$1 PARA COMEÇAR! ✅ Cadastro 100% gratuito ✅ Não precisa comprar curso ✅ Não precisa pagar nenhuma taxa para se cadastrar ✅ Não precisa ter seguidores ✅ Não precisa postar os vídeos na internet ✅ Pode fazer as tarefas de casa…
Video message, posted without a caption
Showing the 2 most recent of 2 posts we hold for @chuvadepremio. 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.
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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“Chuva de prêmios 🤑” (@chuvadepremio), 13,565 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/chuvadepremio.
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.