Channel
@PG_HAOGE
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
1,267subscribers
+84 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002663135587 |
|---|---|
| Type | Channel |
| Username | @PG_HAOGE |
| Created | 24 May 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/PG_HAOGE |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 17:58 | 1,267 | +14 |
| 5 Oct 2026, 01:18 | 1,253 | +8 |
| 26 Sept 2026, 03:59 | 1,245 | +7 |
| 15 Sept 2026, 08:22 | 1,238 | +9 |
| 11 Sept 2026, 16:20 | 1,229 | +5 |
| 7 Sept 2026, 08:14 | 1,224 | +7 |
| 2 Sept 2026, 19:37 | 1,217 | -4 |
| 30 Aug 2026, 11:13 | 1,221 | +4 |
| 27 Aug 2026, 11:07 | 1,217 | +10 |
| 24 Aug 2026, 00:36 | 1,207 | +4 |
| 20 Aug 2026, 04:58 | 1,203 | +2 |
| 17 Aug 2026, 09:46 | 1,201 | +6 |
| 13 Aug 2026, 13:47 | 1,195 | +6 |
| 10 Aug 2026, 19:11 | 1,189 | +5 |
| 8 Aug 2026, 00:07 | 1,184 | +1 |
| 7 Aug 2026, 23:31 | 1,183 | no change |
| 7 Aug 2026, 17:30 | 1,183 | first reading |
5 posts held, back to 24 May 2025 — 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
🗓 07/08/26 🕐 12pm - 2am. 📩 请 PM 豪 哥 询 问 详 情 哟 💬 ─────────────── ✅ 𝐖𝐡𝐚𝐭𝐬𝐀𝐩𝐩 客 服 ✆ 👉 http://wa.me/601118724980 ✅ 𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦 客 服 ➣ 👉 https://t.me/no1_e3cort ✅ 𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦 (FR) 战 报 频 道 ➣ 👉 https://t.me/cindy_lovefr
Video, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Channel created
Showing the 5 most recent of 5 posts we hold for @PG_HAOGE. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“豪哥 ❤️ 槟城” (@PG_HAOGE), 1,267 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/PG_HAOGE.
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.