Channel
@pigongqun
On this record: Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
68,219subscribers
-226 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001880410358 |
|---|---|
| Type | Channel |
| Usernames | @pidanbao @pigongqun @xgpgq |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/pigongqun |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 11:03 | 68,219 | no change |
| 17 Aug 2026, 10:43 | 68,219 | -21 |
| 16 Aug 2026, 14:22 | 68,240 | -21 |
| 15 Aug 2026, 20:39 | 68,261 | no change |
| 15 Aug 2026, 20:35 | 68,261 | -19 |
| 14 Aug 2026, 21:33 | 68,280 | -3 |
| 14 Aug 2026, 09:26 | 68,283 | no change |
| 14 Aug 2026, 09:14 | 68,283 | -26 |
| 13 Aug 2026, 09:45 | 68,309 | -3 |
| 13 Aug 2026, 03:05 | 68,312 | no change |
| 12 Aug 2026, 22:28 | 68,312 | -15 |
| 12 Aug 2026, 12:43 | 68,327 | -9 |
| 12 Aug 2026, 04:06 | 68,336 | -30 |
| 11 Aug 2026, 22:22 | 68,366 | -5 |
| 11 Aug 2026, 12:32 | 68,371 | -7 |
| 11 Aug 2026, 03:06 | 68,378 | no change |
| 10 Aug 2026, 23:22 | 68,378 | -17 |
| 10 Aug 2026, 10:42 | 68,395 | -12 |
| 9 Aug 2026, 23:35 | 68,407 | no change |
| 9 Aug 2026, 23:31 | 68,407 | first reading |
20 posts held, back to 27 March 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 25 pagesof 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 10 June 2026. An engagement rate over an empty window would be a number about nothing.
🦁【西瓜皮担保】 公群总导航🏑 【列表官方认证，不在公群列表的均为假冒、骗子】 ✅公群唯一负责人认证🆔 @abou ⚜️技术服务：1.全球包网 2.软件/平台搭建 3.机器人 4.域名 5.服务器 6.定制IP/签名上架 7.远控/报du 8.API游戏商 ⚜️代收代付：1.码接回u 2.一道卡接回u 3.二道卡接回u 4.APP跑分 5.微信/支付宝代付 6.收u放料 ⚜️卡商公群： 1.大卡商 2.小卡商 ⚜️白资公群：1.白资换汇 2.白资代付 3.白资收u ⚜️承兑公群：1.现金承兑 2.门票核销 3.礼品卡 4.现金滴滴 5.平台币/直播币核销 ⚜️出海资源： 1.全球支付通道(正规BC) 2.代投投放(投流/工具) 3.移民/留学/永居 4.引流/海外粉 5.海外数据 6.海外代购 ⚜️常规服务： 1.天眼查 2.接码实名 3.恋爱/包养/空降 4.美工设计 5.ID贷款 6.票务代付 7.解封类 8…
1
1
1
1
1
1
1
1
1
1
1
Showing the 12 most recent of 20 posts we hold for @pigongqun. 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.
@pigongqun edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 52,603 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 5 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“西瓜皮公群频道 @abou” (@pigongqun), 68,219 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/pigongqun.
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.