Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔥【跑跑Pay官方招商群】跑跑Pay 线上跑分 支付宝 微信高点位代收款

Supergroup

🔥【跑跑Pay官方招商群】跑跑Pay 线上跑分 支付宝 微信高点位代收款

@PP_Pay_crowd1

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

1,495members

+26 since we began measuring on 7 August 2026

2 online right now

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

Register entry

Telegram ID-1001953593267
TypeSupergroup
Username@PP_Pay_crowd1
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 September 2026
Last confirmed live1 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/PP_Pay_crowd1

Topic

Hacking & security — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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

1,4501,5221,4867 August 2026 — 1,469 members8 August 2026 — 1,465 members11 August 2026 — 1,456 members14 August 2026 — 1,453 members17 August 2026 — 1,450 members20 August 2026 — 1,452 members24 August 2026 — 1,451 members27 August 2026 — 1,462 members30 August 2026 — 1,452 members2 September 2026 — 1,459 members8 September 2026 — 1,456 members12 September 2026 — 1,461 members25 September 2026 — 1,491 members28 September 2026 — 1,491 members4 October 2026 — 1,505 members10 October 2026 — 1,522 members14 October 2026 — 1,512 members17 October 2026 — 1,508 members20 October 2026 — 1,500 members23 October 2026 — 1,501 members25 October 2026 — 1,504 members29 October 2026 — 1,499 members1 November 2026 — 1,495 members1,4957 August 20261 November 2026
23 measurements spanning 86 days, net +26. 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 1,439–1,533 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
1 Nov 2026, 06:361,495-4
29 Oct 2026, 09:291,499-5
25 Oct 2026, 21:441,504+3
23 Oct 2026, 08:101,501+1
20 Oct 2026, 16:511,500-8
17 Oct 2026, 05:561,508-4
14 Oct 2026, 09:281,512-10
10 Oct 2026, 19:591,522+17
4 Oct 2026, 18:581,505+14
28 Sept 2026, 03:161,491no change
25 Sept 2026, 09:211,491+30
12 Sept 2026, 11:211,461+5
8 Sept 2026, 08:381,456-3
2 Sept 2026, 20:451,459+7
30 Aug 2026, 16:491,452-10
27 Aug 2026, 19:121,462+11
24 Aug 2026, 10:221,451-1
20 Aug 2026, 22:421,452+2
17 Aug 2026, 16:281,450-3
14 Aug 2026, 08:261,453first 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.

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

“🔥【跑跑Pay官方招商群】跑跑Pay 线上跑分 支付宝 微信高点位代收款” (@PP_Pay_crowd1), 1,495 members as measured 1 November 2026. Telegram Register, tgregister.com/channel/PP_Pay_crowd1.

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.