Photo, posted without a caption

Channel
PUSKIN. Analista Deportivo
@betplaywinner01
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,021subscribers
-219 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 | -1001214584043 |
|---|---|
| Type | Channel |
| Username | @betplaywinner01 |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/betplaywinner01 |
Topic
Sports — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 18:37 | 2,021 | -17 |
| 3 Nov 2026, 12:39 | 2,038 | -6 |
| 31 Oct 2026, 10:56 | 2,044 | -5 |
| 28 Oct 2026, 14:35 | 2,049 | -9 |
| 25 Oct 2026, 06:30 | 2,058 | -1 |
| 22 Oct 2026, 14:28 | 2,059 | -5 |
| 19 Oct 2026, 01:48 | 2,064 | -10 |
| 15 Oct 2026, 21:29 | 2,074 | -4 |
| 13 Oct 2026, 03:45 | 2,078 | -9 |
| 6 Oct 2026, 21:19 | 2,087 | -13 |
| 29 Sept 2026, 19:22 | 2,100 | -29 |
| 19 Sept 2026, 14:59 | 2,129 | -7 |
| 15 Sept 2026, 03:37 | 2,136 | -12 |
| 11 Sept 2026, 04:41 | 2,148 | -14 |
| 5 Sept 2026, 23:41 | 2,162 | -7 |
| 1 Sept 2026, 22:56 | 2,169 | -16 |
| 30 Aug 2026, 04:28 | 2,185 | -7 |
| 26 Aug 2026, 22:24 | 2,192 | -6 |
| 24 Aug 2026, 03:16 | 2,198 | -9 |
| 20 Aug 2026, 19:04 | 2,207 | first reading |
Engagement
20 posts held, back to 4 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Photo, posted without a caption
Nuestro Instagram
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @betplaywinner01. 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“PUSKIN. Analista Deportivo” (@betplaywinner01), 2,021 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/betplaywinner01.
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.