Telegram RegisterThe public register of Telegram
Telegram profile photo for ⚽️ PHOENIX BET ⚽️🔞

Channel

⚽️ PHOENIX BET ⚽️🔞

@phoenibet

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

7,607subscribers

-189 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001509494176
TypeChannel
Username@phoenibet
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live10 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/phoenibet

Growth

7,6077,7967,701.512 August 2026 — 7,796 subscribers12 August 2026 — 7,792 subscribers16 August 2026 — 7,764 subscribers20 August 2026 — 7,748 subscribers23 August 2026 — 7,724 subscribers25 August 2026 — 7,724 subscribers26 August 2026 — 7,693 subscribers30 August 2026 — 7,673 subscribers1 September 2026 — 7,650 subscribers5 September 2026 — 7,633 subscribers10 September 2026 — 7,607 subscribers12 August 202610 September 2026
11 measurements spanning 29 days, net -189. 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 7,579–7,824 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 08:217,607-26
5 Sept 2026, 09:187,633-17
1 Sept 2026, 15:387,650-23
30 Aug 2026, 00:547,673-20
26 Aug 2026, 17:227,693-31
25 Aug 2026, 22:097,724no change
23 Aug 2026, 13:537,724-24
20 Aug 2026, 00:067,748-16
16 Aug 2026, 17:347,764-28
12 Aug 2026, 16:247,792-4
12 Aug 2026, 01:017,796first reading

Engagement

No public post preview. We read this entry on 28 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

GOLDEST BET 🏓⚽️🎾
@GOLDERPUNT · 947,188
Telegram ranks this channel #19 of 60 here — alongside 59 others — read 12 August 2026
BetGenius
@theonlybetgenius · 41,293
Telegram ranks this channel #40 of 66 here — alongside 65 others — read 29 August 2026
Kenyan memes Channel Official
@jokersmokermemes001 · 62,105
Telegram ranks this channel #51 of 58 here — alongside 57 others — read 21 August 2026
SPORTYBET
@sportybetafrikaaa · 38,372
Telegram ranks this channel #59 of 72 here — alongside 71 others — read 1 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“⚽️ PHOENIX BET ⚽️🔞” (@phoenibet), 7,607 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/phoenibet.

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.