Video, posted without a caption

Channel
Divino Radio ⚽⚾🏀🏇🏻🏒
@divinoradio
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry
1,175subscribers
-202 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 | -1003399663560 |
|---|---|
| Type | Channel |
| Username | @divinoradio |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/divinoradio |
Topic
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 11 Oct 2026, 11:58 | 1,175 | -17 |
| 5 Oct 2026, 13:16 | 1,192 | -34 |
| 27 Sept 2026, 16:00 | 1,226 | -36 |
| 15 Sept 2026, 10:39 | 1,262 | -4 |
| 12 Sept 2026, 03:00 | 1,266 | -13 |
| 7 Sept 2026, 13:40 | 1,279 | -16 |
| 2 Sept 2026, 20:36 | 1,295 | -10 |
| 30 Aug 2026, 12:06 | 1,305 | -11 |
| 27 Aug 2026, 12:08 | 1,316 | -15 |
| 24 Aug 2026, 02:54 | 1,331 | -1 |
| 20 Aug 2026, 16:35 | 1,332 | -7 |
| 18 Aug 2026, 01:06 | 1,339 | -19 |
| 14 Aug 2026, 15:27 | 1,358 | -13 |
| 10 Aug 2026, 19:27 | 1,371 | -8 |
| 8 Aug 2026, 04:24 | 1,379 | +2 |
| 7 Aug 2026, 22:18 | 1,377 | no change |
| 7 Aug 2026, 18:31 | 1,377 | first reading |
Engagement
20 posts held, back to 3 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 3m 21s
- Average length
- 34s
Measured directly from 6 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.
Reaction mix
73 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 42.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 31 | 42.5% | |
| ❤ | 23 | 31.5% | |
| 🔥 | 13 | 17.8% | |
| ⚡ | 2 | 2.74% | |
| 🏆 | 2 | 2.74% | |
| 👏 | 2 | 2.74% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 12 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 73 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 3 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Photo, posted without a caption
La Directa MLB VIP de hoy (07/08) de Dato Deportivo: 🔥 ⚾ Colorado Rockies Vs. St. Louis Cardinals Jugamos: St. Louis Cardinals a Ganar (Moneyline) https://www.divinobet.vip
❤3🔥2
Divino Radio ⚽⚾🏀🏇🏻🏒 pinned a photo
Boston dejó en el terreno a Chicago logrando el Divino Acierto 🤑 ⚾ ¡Victoria infartante en casa y a cobrar con carácter en la zona VIP! Los Red Sox batallaron durante 13 entradas enteras en el Fenway Park, levantaron el partido cinco veces y sellaron el triunfo en extrainnings para mantener la racha ganadora. Asegura tu posición VIP en https://www.DivinoBet.VIP
👍4❤2
Nos vemos hoy por @divinoradio (Instagram). Una cita imperdible 🤑🫰🏼
Photo, posted without a caption
La Directa MLB VIP de hoy (06/08) de Dato Deportivo: 🔥 ⚾ Chicago White Sox Vs. Boston Red Sox Jugamos: Boston Red Sox a Ganar (Moneyline) https://www.divinobet.vip
Divino Radio ⚽⚾🏀🏇🏻🏒 pinned Deleted message
¡Aprovecha nuestra promo de hoy! 🤑🫰🏼
Tampa Bay mandó en Denver 🫰🏼⚾ Blanqueo en la carretera y a cobrar en la zona VIP. Los Rays de impusieron desde el primer lanzamiento en Denver y el triunfo visitante se cumplió sin sobresaltos para sumar un nuevo éxito a la cuenta exclusiva. Tu próxima jugada VIP te espera en https://www.DivinoBet.VIP
👍5
La Directa MLB VIP de hoy (05/08) de Dato Deportivo: 🔥 ⚾ Tampa Bay Rays Vs. Colorado Rockies Jugamos: Tampa Bay Rays a Ganar (Moneyline) https://www.divinobet.vip
👍5❤2🔥2
Showing the 12 most recent of 20 posts we hold for @divinoradio. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@divinoradio named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Divino Radio ⚽⚾🏀🏇🏻🏒” (@divinoradio), 1,175 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/divinoradio.
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.