What do you want to see on the channel?
- Football betting99%
- Tennis betting1%
- Esports betting0%
- Political betting0%
Shares as published. No per-option vote count is published by Telegram, so none is shown.

Channel
@bettibot
On this record: Growth · Engagement · What this channel posts · Posts · Polls · Cite this entry
171subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001083619410 |
|---|---|
| Type | Channel |
| Username | @bettibot |
| Created | Between 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/bettibot |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 05:23 | 171 | -3 |
| 16 Aug 2026, 17:59 | 174 | -3 |
| 8 Aug 2026, 13:45 | 177 | no change |
| 7 Aug 2026, 13:46 | 177 | first reading |
20 posts held, back to 30 September 2017 — 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 pageof 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 27 December 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
What do you want to see on the channel?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Sticker, posted without a caption
Signed Ilya Stetsyuk
Who will win? (03.01.18) 🆔 @bettibot X – 8 👍👍👍👍👍👍👍 42% Chelsea FC – 6 👍👍👍👍👍 32% Arsenal FC – 5 👍👍👍👍 26% 👥 19 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (12.01.18) 🆔 @bettibot Getafe – 5 👍👍👍👍👍👍👍 71% X – 1 👍 14% Malaga – 1 👍 14% 👥 7 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (12.11.17) 🆔 @bettibot Anthony Pettis – 15 👍👍👍👍👍👍👍 52% Dustin Poirier – 9 👍👍👍👍 31% X – 5 👍👍 17% 👥 29 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (28.10.17) 🆔 @bettibot Juventus – 87 👍👍👍👍👍👍👍 73% AC Milan – 23 👍👍 19% X – 9 👍 8% 👥 119 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (05.11.17) 🆔 @bettibot Manchester Utd – 284 👍👍👍👍👍👍👍 66% Chelsea FC – 124 👍👍👍 29% X – 21 👍 5% 👥 429 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (05.11.17) 🆔 @bettibot Manchester City – 187 👍👍👍👍👍👍👍 67% Arsenal FC – 72 👍👍👍 26% X – 19 👍 7% 👥 278 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (05.11.17) 🆔 @bettibot Real Madrid – 10 👍👍👍👍👍👍👍 71% X – 4 👍👍👍 29% UD Las Palmas ▫️ 0% 👥 14 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (04.11.17) 🆔 @bettibot FC Barcelona – 10 👍👍👍👍👍👍👍 100% X ▫️ 0% FC Sevilla ▫️ 0% 👥 10 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (21.10.17) 🆔 @bettibot Manchester Utd – 210 👍👍👍👍👍👍👍 86% Huddersfield Town – 21 👍 9% X – 14 ▫️ 6% 👥 245 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Who will win? (28.10.17) 🆔 @bettibot FC Barcelona – 96 👍👍👍👍👍👍👍 82% X – 12 👍 10% Athletic Club – 9 👍 8% 👥 117 people voted so far. Poll closed.
Signed Ilya Stetsyuk
Showing the 12 most recent of 20 posts we hold for @bettibot. 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.
What do you want to see on the channel?
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 30 September 2017 to 27 December 2025. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“BETTING EXPERT” (@bettibot), 171 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/bettibot.
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.