Telegram RegisterThe public register of Telegram
Telegram profile photo for 📣 平安【供需】项目大全

Channel

📣 平安【供需】项目大全

@pingan_gy

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

24,384subscribers

-8,760 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-1001434299839
TypeChannel
Usernames@pingan_gy @ppaagx
Description➩ 公群导航 @ppaadh ➩ 新开公群 @ppaaxq ➩ 供需频道 @ppaagx ➩ 国内大群 @ppaadq ➩ 公告频道 @vip999 ✅ 智能群管 @ppaa 24小时自助交易
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held128
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/pingan_gy

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

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 4 other registered channels. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qdvip/79726 Aug 2026, 10:32 UTC@pingan_gy/25267 · this entry6 Aug 2026, 12:04 UTC1.001.5 hours
@pingan_gy/25264 · this entry6 Aug 2026, 09:38 UTC@qdvip/79847 Aug 2026, 04:35 UTC1.0019 hours
@pingan_gy/25296 · this entry11 Aug 2026, 11:16 UTC@qdvip/805612 Aug 2026, 09:20 UTC1.0022 hours
@pingan_gy/25436 · this entry6 Sept 2026, 12:00 UTC@qdvip/855819 Sept 2026, 10:35 UTC1.0013 days
@qdvip/90886 Nov 2026, 10:36 UTC@pingan_gy/25789 · this entry6 Nov 2026, 12:04 UTC1.0089 minutes
@qdvip/91289 Nov 2026, 09:01 UTC@pingan_gy/25807 · this entry9 Nov 2026, 09:03 UTC1.002 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@qdvip17 (8/8 hand-verifiable sample passed)0.9921 minutesthis entry (12–5)
@HQWE0017 (8/8 hand-verifiable sample passed)0.997 minutesthis entry (13–4)
@kuaishou15 (8/8 hand-verifiable sample passed)1.005 minutesthis entry (11–4)
@fafafa11 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (11–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 13 of the 13 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 438 comparable posts for this entry, running 5 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @pingan_gy — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

24,38433,14428,7647 August 202615 November 2026
128 measurements spanning 100 days, net -8,760. 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 23,070–34,458 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 128
Measured (UTC)SubscribersChange
15 Nov 2026, 21:0124,384-47
14 Nov 2026, 16:0724,431-112
12 Nov 2026, 14:1624,543-99
11 Nov 2026, 19:4024,642-78
10 Nov 2026, 14:1624,720-12
9 Nov 2026, 23:5724,732-25
9 Nov 2026, 02:2824,757-1
8 Nov 2026, 16:0024,758-73
7 Nov 2026, 15:5724,831-9
7 Nov 2026, 12:0124,840-115
6 Nov 2026, 18:4824,955-1
6 Nov 2026, 13:2724,956-36
5 Nov 2026, 20:5924,992no change
5 Nov 2026, 14:4524,992-15
4 Nov 2026, 20:4925,007-12
4 Nov 2026, 12:3125,019-33
3 Nov 2026, 17:1825,052-28
3 Nov 2026, 09:4825,080-9
2 Nov 2026, 16:2825,089-9
2 Nov 2026, 10:3625,098first reading

Engagement

556 posts held, back to 5 August 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 166 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.80%
avg views ÷ 24,384 subscribers
Avg views / post
439
164 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
164
of 556 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held556 (5 August 2026 – 16 November 2026)
Views total71,934
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 22:07 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Links
≈1,060

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 164 posts held from the last 30 days (0.61%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 12:59 UTC114 viewsread 16 November 2026

😎😀😀😀😀😎 😂公群 完美电子🎰捕鱼 😂公群 完美经典2.0PC🇨🇦 😂公群 完美满赔PC28🇨🇦 😂公群 完美2.8倍PC🇨🇦 😂😂公群 完美16倍红包牛牛🧧 😂😂公群 完美网盘pc🇨🇦 😂😂公群 完美手摇快三🎲 😁PC/骰子客服👉 @yongli333 😁电子类客服 👉 @xj666777 😀😀😀😂😂😂😂😂😂😀 😀😀😀😀😀😀😀😀😀😀😀😀😀😀

16 Nov 2026, 12:01 UTC141 viewsread 16 November 2026

⭐️ ⭐️ ⭐️ 🫥🫥🫥🫥⭐️ ⭐️ ⭐️ 🫥🫥🫥🫥🫥 总押490万U @okgame 💵取款通道: 🇨🇦新宝PC28合集 @xb28 🎲新宝快三扫雷合集 @k3k3 🇨🇦新宝5.0高倍5.0/4.6 🇨🇦新宝2.0高倍4.755/4.32 🇨🇦新宝2.84高倍6.78/6.32 🇨🇦新宝2.0超级满赔4.75/4.315 🇨🇦新宝2.0满赔组合遇13/14赔2.7倍 🇨🇦新宝超满赔网盘组合遇13/14中奖正常赔付4.315/3.7 🫥OK扫雷游戏·5万限红 🎲新宝群骰子快三游戏 🔥新宝2.0满赔哈希4.73/4.31 🫥 新宝娱乐综合盘🎰 @xbyl 🫥🤖新宝电子🎰 @xbdz 🇨🇦PC/骰子客服👉@x111 🎰电子类客服👉 @x444 😃有担保更放心 大额无忧! 新宝娱乐 · 三年沉淀,感谢信任,一路同行! 🫥🫥🫥🫥🫥🫥 为保障您的资金安全,请务必通过官方导航 @ok28 加入游戏公群! 🫥 验

16 Nov 2026, 09:04 UTC149 viewsread 16 November 2026

😀😀😀😀😀😀😀 😀😀😀 😀😀😀 😂😂😂😂😂 信赖品牌|出款无忧|与您同行 ⭐️主营游戏: OK游戏中心总押260万U🔥 🌝NG娱乐上下分群总押260万U 😂PC2.0超满赔 😂PC2.0网盘(万反92) 😂PC5.0高倍 😂PC2.847高倍 😂PC2.0/13.14赔2.7 👉 OK游戏中心人民币电子 @N888 😂😂😂😂😂 @ppcc 😂😂😂😂😂 @pcpc 达利游戏中心总押60万U 🔥 999公群 NG娱乐上下分总群总押60万U 热门PC全覆盖 😂彩种多样化: 开设多个不同赔率PC公群,涵盖所有热门玩法可供选择。 😂赔率新标杆: 领跑行业的赔率矩阵,打破盈利天花板,助您成就巅峰战绩 保持初心,多年经营 🌝为所有玩家构筑一个公平,高效,安全的娱乐净土 🌝NG娱乐 专业·公平·安全——值得信赖的基石 🌝 原班人马继续为您服务,一路同行,风雨同舟 😇😇😇😇😇😇😇😆

16 Nov 2026, 07:58 UTC163 viewsread 16 November 2026

钉钉数据 微拉数据 支拉数据🔥🔥🔥 华侨数据🔥🔥🔥 快递数据 快递解密 全球Tg数据 全球ws数据 每日百万数据更新 以上数据可过地址男女全名年纪 地区可屏蔽可指定 运营商/年龄段可指定 数据商:@mhd689

16 Nov 2026, 07:04 UTC181 viewsread 16 November 2026

纯进口印度双效伟哥/崔情/安眠/壮阳/早泻/延时/助勃/保健品 真货 https://t.me/weige_dajiba

16 Nov 2026, 05:40 UTC197 viewsread 16 November 2026

营业厅内部办白名单手机卡,可以打打电销! 出售各种手机卡 香港流量卡 各国免实名的卡 注册卡(工作室专用) https://t.me/taiyang1233211

15 Nov 2026, 12:59 UTC297 viewsread 16 November 2026

😎😀😀😀😀😎 😂公群 完美电子🎰捕鱼 😂公群 完美经典2.0PC🇨🇦 😂公群 完美满赔PC28🇨🇦 😂公群 完美2.8倍PC🇨🇦 😂😂公群 完美16倍红包牛牛🧧 😂😂公群 完美网盘pc🇨🇦 😂😂公群 完美手摇快三🎲 😁PC/骰子客服👉 @yongli333 😁电子类客服 👉 @xj666777 😀😀😀😂😂😂😂😂😂😀 😀😀😀😀😀😀😀😀😀😀😀😀😀😀

15 Nov 2026, 12:03 UTC287 viewsread 16 November 2026

⭐️ ⭐️ ⭐️ 🫥🫥🫥🫥⭐️ ⭐️ ⭐️ 🫥🫥🫥🫥🫥 总押400万U @okgame 💵取款通道: 🇨🇦新宝PC28合集 @xb28 🎲新宝快三扫雷合集 @k3k3 🇨🇦新宝5.0高倍5.0/4.6 🇨🇦新宝2.0高倍4.755/4.32 🇨🇦新宝2.84高倍6.78/6.32 🇨🇦新宝2.0超级满赔4.75/4.315 🇨🇦新宝2.0满赔组合遇13/14赔2.7倍 🇨🇦新宝超满赔网盘组合遇13/14中奖正常赔付4.315/3.7 🫥OK扫雷游戏·5万限红 🎲新宝群骰子快三游戏 🔥新宝2.0满赔哈希4.73/4.31 🫥 新宝娱乐综合盘🎰 @xbyl 🫥🤖新宝电子🎰 @xbdz 🇨🇦PC/骰子客服👉@x111 🎰电子类客服👉 @x444 😃有担保更放心 大额无忧! 新宝娱乐 · 三年沉淀,感谢信任,一路同行! 🫥🫥🫥🫥🫥🫥 为保障您的资金安全,请务必通过官方导航 @ok28 加入游戏公群! 🫥 验

15 Nov 2026, 09:10 UTC263 viewsread 16 November 2026

收全平台全系列色粉 打全网码 打Q群 所有渠道都可收 长期稳定包量 陌陌 微博 抖音 快手 探探 皮皮虾 b站 今日头条 soul 赫兹 陌陌v转 探探v转 百合 对缘 爱聊 珍爱 心遇 她伴 等各大相亲平台色粉 梦幻 天龙八步 问道 逆水寒等等 各大游戏粉 抖音 陌陌 探探 等主流平台色 欢迎各大中介 一手工作室来打粉 稳定打款 假粉走远点 各种收粉聊天小平台,相亲粉 天马 v扫 q扫 浏览器 无限开 打量联系 : @kanfan 永存收粉频道: https://t.me/zouzai 点加入防丢失 公群: https://t.me/+YbtKr5ntkaMxM2U5

15 Nov 2026, 09:00 UTC263 viewsread 16 November 2026

😀😀😀😀😀😀😀 😀😀😀 😀😀😀 😂😂😂😂😂 信赖品牌|出款无忧|与您同行 ⭐️主营游戏: OK游戏中心总押260万U🔥 🌝NG娱乐上下分群总押260万U 😂PC2.0超满赔 😂PC2.0网盘(万反92) 😂PC5.0高倍 😂PC2.847高倍 😂PC2.0/13.14赔2.7 👉 OK游戏中心人民币电子 @N888 😂😂😂😂😂 @ppcc 😂😂😂😂😂 @pcpc 达利游戏中心总押60万U 🔥 999公群 NG娱乐上下分总群总押60万U 热门PC全覆盖 😂彩种多样化: 开设多个不同赔率PC公群,涵盖所有热门玩法可供选择。 😂赔率新标杆: 领跑行业的赔率矩阵,打破盈利天花板,助您成就巅峰战绩 保持初心,多年经营 🌝为所有玩家构筑一个公平,高效,安全的娱乐净土 🌝NG娱乐 专业·公平·安全——值得信赖的基石 🌝 原班人马继续为您服务,一路同行,风雨同舟 😇😇😇😇😇😇😇😆

15 Nov 2026, 08:11 UTC264 viewsread 16 November 2026

😂😂😂😂 项目名称: 🥰微信兼职三人小群,(客服代建模式)不用换tou像不用改名字📱📱📱 纯兼职粉不风控 不风控 不风控 项目介绍: 🥰提供数据去添加客户,通过了创群,把客户、客服拉倒群里即可🥰 不用换tou像不用改名字⚠️实时数据、通过率10/8⚠️ 欢迎团队、工作室合作🥰 价格: 🥰 单价😁😁、单号日入利润😂😂😂+ 结账方式: 👍、👍、📱 晚上10:00结账👍👍 业务员:@Bai4086 业务对接群:https://t.me/+yPiXeVvuKow5NDBl 担保群链接:https://t.me/+ek8CLu9yE003MTNh

15 Nov 2026, 06:15 UTC263 viewsread 16 November 2026

😆😆😆😆: 😆😆😆公群 😆😆: 😆😆😆😆😆 公群名称 :628公群已押500u【微信三人群代建模式 收团/机房《实时数据10过7》】 业务类型:微信拉群 公群链接:https://t.me/+L4XgjTANP8M2NWVh 业务对接:@lh4490

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

@pingan_gy 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
29 September 2026
Most recent edit
29 September 2026

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

“📣 平安【供需】项目大全” (@pingan_gy), 24,384 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/pingan_gy.

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.