Telegram RegisterThe public register of Telegram
Telegram profile photo for PGA集团 - 白马会通知频道

Channel

PGA集团 - 白马会通知频道

@pgapay1

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

847subscribers

-50 since we began measuring on 16 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001384524648
TypeChannel
Username@pgapay1
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live3 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/pgapay1

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

84789787216 August 2026 — 897 subscribers16 August 2026 — 897 subscribers25 August 2026 — 894 subscribers1 September 2026 — 891 subscribers10 September 2026 — 882 subscribers19 September 2026 — 879 subscribers3 October 2026 — 847 subscribers16 August 20263 October 2026
7 measurements spanning 48 days, net -50. 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 840–905 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 13:17847-32
19 Sept 2026, 01:19879-3
10 Sept 2026, 22:37882-9
1 Sept 2026, 04:34891-3
25 Aug 2026, 11:24894-3
16 Aug 2026, 19:30897no change
16 Aug 2026, 19:15897first reading

Engagement

20 posts held, back to 18 June 2026 — 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 20 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
30s
Average length
30s

Measured directly from 1 video 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 2 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 18 June 2026 to 17 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

17 Jul 2026, 07:49 UTC467 views0 reactionsread 16 August 2026
Photo

京东微信单ios 通道编码 93 限额 500 1000

11 Jul 2026, 01:37 UTC691 viewsread 16 August 2026
Video

【产品名称】:红豆卡 (🚩京东卡密🚩) 【固定金额】:10,20,30,50,100,200 【通道编码】:62 (京东卡0纠纷原价) 【通道成率】: 60%(24小时不停机) 【支付方式】: 🚩微信支付 🚩京东APP内可🚩绑卡支付.🚩云闪付.🚩数字人民币.🚩QQ支付.🚩白条支付 【卡密通道规则】:全层抗投诉 抗并发 🈲PC端 (只接正规BC,QP,🈲刷单,🈲话费卷,🈲资金盘,🈲三黑,🈲大头贴客户,🈲电诈。发现混料一律不下发,1-10倍赔付)混料判定售卡店铺提供被害人聊天记录。 以下为充值 【支付流程】 1:根据🏦收银台下单页面流程-提示跳转🚩京东APP,购买相应金额的💳卡密-选择支付方式进行订单支付✅; 2:付款成功后✔️,🚩京东App--我的订单--全部订单--找到该订单点击详情内—查看卡密复制;🔄返回收银台页面提交💳卡号卡密,请等待⌛️卡密完成即立刻上分💹! 3: 会员无法商品下单,显示销售火爆,是因🚩京东账号未绑定实…

1 Jul 2026, 16:01 UTC438 viewsread 16 August 2026

京东微信单ios 通道编码 92 限额 200 300 500 1000 京东微信单ios 通道编码 93 限额 500 1000 通道名称】:红豆卡(24小时不日切) 【通道编码】:62 【通道金额】:10-20-30-50-100-200

29 Jun 2026, 16:01 UTC346 viewsread 16 August 2026

京东微信单ios 通道编码 92 限额 200 300 500 1000 京东微信单ios 通道编码 93 限额 500 1000 通道名称】:红豆卡(24小时不日切) 【通道编码】:62 【通道金额】:10-20-30-50-100-200

28 Jun 2026, 16:29 UTC508 viewsread 16 August 2026
Photo

92 93 微信单端 ios 成率持续优化 继续上量上并发了

27 Jun 2026, 16:01 UTC307 viewsread 16 August 2026

京东微信单ios 通道编码 92 限额 200 300 500 1000 京东微信单ios 通道编码 93 限额 500 1000 通道名称】:红豆卡(24小时不日切) 【通道编码】:62 【通道金额】:10-20-30-50-100-200

26 Jun 2026, 16:10 UTC494 viewsread 16 August 2026
Photo

90暂时开不了 92 93 微信单端ios 成率超稳 可以开启来

Showing the 12 most recent of 20 posts we hold for @pgapay1. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 3 October 2026 — this entry's latest reading, not the date you are reading this.

“PGA集团 - 白马会通知频道” (@pgapay1), 847 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/pgapay1.

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.