Telegram RegisterThe public register of Telegram
Telegram profile photo for СТАВКИ НА СПОРТ

Channel

СТАВКИ НА СПОРТ

@Apkallari

On this record: Topic · Growth · Engagement · Posts · Cite this entry

33,448subscribers

-2,036 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001884566765
TypeChannel
Username@Apkallari
Created17 March 2023 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live29 October 2026
Measurements held53
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/Apkallari

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

33,44835,48434,4667 August 2026 — 35,484 subscribers7 August 2026 — 35,484 subscribers8 August 2026 — 35,452 subscribers9 August 2026 — 35,430 subscribers10 August 2026 — 35,409 subscribers11 August 2026 — 35,382 subscribers12 August 2026 — 35,355 subscribers13 August 2026 — 35,340 subscribers14 August 2026 — 35,296 subscribers16 August 2026 — 35,251 subscribers17 August 2026 — 35,222 subscribers18 August 2026 — 35,197 subscribers19 August 2026 — 35,167 subscribers20 August 2026 — 35,123 subscribers21 August 2026 — 35,096 subscribers23 August 2026 — 35,058 subscribers25 August 2026 — 35,025 subscribers26 August 2026 — 34,998 subscribers27 August 2026 — 34,963 subscribers28 August 2026 — 34,931 subscribers29 August 2026 — 34,917 subscribers30 August 2026 — 34,886 subscribers31 August 2026 — 34,860 subscribers1 September 2026 — 34,828 subscribers2 September 2026 — 34,796 subscribers3 September 2026 — 34,765 subscribers5 September 2026 — 34,717 subscribers8 September 2026 — 34,632 subscribers11 September 2026 — 34,558 subscribers13 September 2026 — 34,513 subscribers14 September 2026 — 34,466 subscribers16 September 2026 — 34,430 subscribers19 September 2026 — 34,374 subscribers25 September 2026 — 34,216 subscribers4 October 2026 — 34,013 subscribers8 October 2026 — 33,905 subscribers13 October 2026 — 33,809 subscribers14 October 2026 — 33,780 subscribers15 October 2026 — 33,759 subscribers16 October 2026 — 33,728 subscribers17 October 2026 — 33,698 subscribers18 October 2026 — 33,684 subscribers19 October 2026 — 33,660 subscribers20 October 2026 — 33,645 subscribers21 October 2026 — 33,627 subscribers22 October 2026 — 33,606 subscribers23 October 2026 — 33,586 subscribers24 October 2026 — 33,564 subscribers25 October 2026 — 33,542 subscribers26 October 2026 — 33,514 subscribers27 October 2026 — 33,494 subscribers28 October 2026 — 33,470 subscribers29 October 2026 — 33,448 subscribers7 August 202629 October 2026
53 measurements spanning 83 days, net -2,036. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 33,143–35,789 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 53
Measured (UTC)SubscribersChange
29 Oct 2026, 17:5533,448-22
28 Oct 2026, 17:2733,470-24
27 Oct 2026, 13:4633,494-20
26 Oct 2026, 11:1433,514-28
25 Oct 2026, 09:0633,542-22
24 Oct 2026, 11:3033,564-22
23 Oct 2026, 11:0633,586-20
22 Oct 2026, 12:1733,606-21
21 Oct 2026, 06:5533,627-18
20 Oct 2026, 08:0633,645-15
19 Oct 2026, 11:2133,660-24
18 Oct 2026, 09:5933,684-14
17 Oct 2026, 12:1433,698-30
16 Oct 2026, 11:2733,728-31
15 Oct 2026, 13:5633,759-21
14 Oct 2026, 14:0433,780-29
13 Oct 2026, 04:0833,809-96
8 Oct 2026, 22:3833,905-108
4 Oct 2026, 10:0234,013-203
25 Sept 2026, 18:3934,216first reading

Engagement

3 posts held, back to 17 March 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 148 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 3 posts for this entry, the most recent from 31 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Mar 2026, 00:59 UTC851 viewsread 29 October 2026
File

🆕 SPINBETTER APK 😎 Promokod➡️ GIFT1000 📺 SPINBETTER.COM🍏

7 Feb 2026, 00:32 UTC≈1,690 viewsread 29 October 2026
File

🆕 APK 🇮🇹 Promokod ➡️ FBL777 📺1WIN.COM 🍏

Showing the 3 most recent of 3 posts we hold for @Apkallari. 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“СТАВКИ НА СПОРТ” (@Apkallari), 33,448 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/Apkallari.

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.