开群日期:7月4日 ⌨:189-西瓜皮担保 供需频道:@xgpyw 公群频道:@xgpgq

Channel
西瓜皮-每日新群
@xgpxq
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
26,295subscribers
-247 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003782226872 |
|---|---|
| Type | Channel |
| Username | @xgpxq |
| Description | 👋交易首选 - 西瓜皮担保 ━━━━━━━━━━━ 🔹 公群导航: @xgpgq 🔹 盘口资源: @xgpyw 🔹 骗子曝光: @xgpbg 🔹 官方公告: @xgpsq 🔹 核心大群: @xgpjlq ━━━━━━━━━━━ 🧑🏻💻 公群-上押: @abou 🧑🏻💻 专群-客服: @achai 🧑🏻💻 供需-客服: @ashua 🧑🏻💻 仲裁-客服: @canjie 🧑🏻💻 投诉-建议: @geren ━━━━━━━━━━━━ 🤖客服中心: @db365bot |
| Created | 7 May 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/xgpxq |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 02:08 | 26,295 | -38 |
| 14 Aug 2026, 09:57 | 26,333 | -31 |
| 13 Aug 2026, 04:56 | 26,364 | -21 |
| 12 Aug 2026, 02:04 | 26,385 | -48 |
| 11 Aug 2026, 03:33 | 26,433 | -59 |
| 10 Aug 2026, 02:27 | 26,492 | -21 |
| 9 Aug 2026, 00:55 | 26,513 | -22 |
| 8 Aug 2026, 01:23 | 26,535 | -7 |
| 7 Aug 2026, 16:47 | 26,542 | first reading |
Engagement
3 posts held, back to 7 May 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 21 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 3 posts for this entry, the most recent from 4 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 16 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
😍😍😍 telegram 灰色圈子交易首选 - 西瓜皮担保 😀电报交易需谨慎, 交易想安心,选西瓜皮担保 😀找资源,找渠道,找盘口,找车队,到西瓜皮担保 😀灰色圈子流量聚集地,一切你想要的资源这里都有 🥰🥰🥰🥰 🥰🥰🥰🥰 😀公群列表 @xgpgq 😀供需盘口 @xgpyw 🥰🥰🥰🥰🥰🥰🥰🥰 😀开通公群联系:@abou 😁 金融级安全交易 · 创新 web3 担保生态 😘😘😘😘 😘😘😘😘
Channel created
Showing the 3 most recent of 3 posts we hold for @xgpxq. 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.
Posts edited after publishing
@xgpxq 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.
- First edit seen
- 9 August 2026
- Most recent edit
- 9 August 2026
Citation-graph rank
Citation-graph rank — 61,892 of 1,481,346entries 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.
Mentions
Named by 2 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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“西瓜皮-每日新群” (@xgpxq), 26,295 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/xgpxq.
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.