Channel
@betport
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001159295743 |
|---|---|
| Type | Channel |
| Username | @betport |
| Description | Прогнозы на спорт от профи. Все о ставках. Денежные конкурсы. www.betport.ru |
| Created | Between 1 March 2018 and 25 August 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/betport |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:03 | 5 | no change |
| 7 Aug 2026, 20:24 | 5 | first reading |
20 posts held, back to 25 August 2019 — 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 23 November 2020. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
Virtus.pro — Vikin.gg: прогноз на матч EPIC League Season 2 Division 1 26 ноября в рамках группового этапа EPIC League Season 2 Division 1 запланирован поединок Virtus.pro — Vikin.gg. Встречаются два лидера турнирной таблицы, причем Virtus.pro так и вовсе еще не проигрывал. Vikin.gg уступает в классе, но команда набрала шикарную форму, и может составить здесь конкуренцию. Virtus.pro Virtus.pro лидирует в турнирной …
Evil Geniuses — OG: прогноз на ½ финала турнира BLAST Premier: Fall 2020 26 октября в полуфинале верхней сетки группы A турнира BLAST Premier: Fall 2020 запланирован поединок Evil Geniuses — OG. Напомним регламент: в группе A четыре команды (EG, OG, Natus Vincere и Ninjas in Pyjamas). Две лучшие команды пройдут в основную часть турнира, а третья и четвертые команды отправятся в BLAST Fall 20202 Showdown. Evil Geniu…
Rogue — JD Gaming: прогноз на матч турнира World Championship
https://betport.ru/besplatnye-prognozy-na-kibersport/astralis-heroic-prognoz-na-plej-off-esl-pro-league-season-12.html
https://betport.ru/besplatnye-prognozy-na-kibersport/complexity-gaming-ence-esports-prognoz-na-plej-off-esl-pro-league-season-12.html
Флуминенсе — Фламенго: прогноз на матч чемпионата Бразилии 10 сентября в девятом туре чемпионата Бразилии состоится встреча «Флуминенсе» — «Фламенго». «Фламенго» имеет впечатляющую серию из шести матчей без поражений. «Флуминенсе» отстает в таблице не так уж серьезно, и вполне может создать конкуренцию. «Флуминенсе» «Флуминенсе» располагается на восьмой позиции в таблице, набрав 11 очков. Пускай команда и отстает о…
https://betport.ru/futbol/ural-krasnodar-prognoz-na-match-chetvertogo-tura-chempionata-rossii.html
https://betport.ru/futbol/kolambus-kryu-minnesota-stavka-na-match-1-8-finala-plej-off-mls.html
https://betport.ru/futbol/benfika-sporting-prognoz-na-match-34-go-tura-chempionata-portugalii.html
https://betport.ru/besplatnye-prognozy-na-kibersport/victory-five-suning-prognoz-na-match-turnira-lol-pro-league.html
Один из наших экспертов решил стрельнуть в даль. Что ж оставим это тут, чтоб не потерять.😎⚽️🏆
в 1/4 бавария юве атлетико мс ______ наполи ливер барса псж
Showing the 12 most recent of 20 posts we hold for @betport. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“BETPORT - Спортивные обзоры.” (@betport), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/betport.
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.