Telegram RegisterThe public register of Telegram
Telegram profile photo for 9PMBET.COM

Channel

9PMBET.COM

@WWW9PMBETCOM

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

10,308subscribers

-79 since we began measuring on 3 September 2026

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

Register entry

Telegram ID-1001973293543
TypeChannel
Username@WWW9PMBETCOM
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/WWW9PMBETCOM

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 17 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 why it has no browse page of its own yet.

Growth

10,30810,38710,347.53 September 2026 — 10,387 subscribers3 September 2026 — 10,387 subscribers4 September 2026 — 10,386 subscribers9 September 2026 — 10,370 subscribers11 September 2026 — 10,353 subscribers13 September 2026 — 10,334 subscribers15 September 2026 — 10,330 subscribers17 September 2026 — 10,308 subscribers3 September 202617 September 2026
8 measurements spanning 14 days, net -79. 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 10,296–10,399 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 14:1710,308-22
15 Sept 2026, 10:0110,330-4
13 Sept 2026, 16:2110,334-19
11 Sept 2026, 23:5710,353-17
9 Sept 2026, 15:5610,370-16
4 Sept 2026, 01:4210,386-1
3 Sept 2026, 12:5310,387no change
3 Sept 2026, 12:4710,387first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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.

Bet585.com Official ®
@Bet585Canal · 78,603
Telegram ranks this channel #85 of 86 here — alongside 85 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“9PMBET.COM” (@WWW9PMBETCOM), 10,308 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/WWW9PMBETCOM.

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.