Telegram RegisterThe public register of Telegram
Telegram profile photo for 苹果担保公群导航 @PGDB

Channel

苹果担保公群导航 @PGDB

@pgdb

2 usernames

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

195subscribers

-1 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1001487731503
TypeChannel
Usernames@pgdb @pingguodanbao
Created18 July 2020measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live23 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/pgdb

Growth

195196195.515 August 2026 — 196 subscribers16 August 2026 — 196 subscribers23 August 2026 — 195 subscribers15 August 202623 August 2026
3 measurements spanning 8 days, net -1. 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 195–196 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 19:25195-1
16 Aug 2026, 17:03196no change
15 Aug 2026, 08:32196first reading

Engagement

5 posts held, back to 18 July 2020the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 5 posts for this entry, the most recent from 6 March 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Mar 2024, 10:18 UTC≈7,740 viewsread 15 August 2026

苹果担保公群列表 [苹果担保] 公群分类导航 🎊 手机口①类公群 🎊 远程短信 短信口 🎊 租Q/抖音 租号类公群 🎊 微信账密/PC类公群 🎊 话术单类公群 🎊 抖音/第三方引流类公群 🎊短信/IM类公群 🎊 跑分/代收/代付类公群 🎊 QQ拉手/支拉/V拉类公群 🎊电销/香烟类公群 🎊群码/红包手公群 🎊呼叫转移类类公群 🎊苹果ID类公群 🎊查档/数据类公群 🎊能量trx兑换公群 🎊地推类公群 🎊TG引流类公群 🎊游戏娱乐类公群 🎊出国劳务类公群 🎊外围/裸聊类公群 🎊其他类接码解封帐号类 ‼️做单聊天记录一定要及时截图 ————【免费投诉 @pgdbjf】

5 Mar 2024, 14:56 UTC≈6,200 viewsread 15 August 2026

欧易官方网站 https://www.okx.com/ 如网站不能浏览请关闭加速器或更换浏览器 ! ✅欧易官方Telegram频道: https://t.me/OKXGroup_CN 安卓用户可以直接到官方下载 冷钱包下载地址 https://ownbit.io 好处如下💰 转账需要TRX,手续费低,转账快无需等待。 适合老用户,新用户建议使用欧易. 坏处如下⚠️ 使用不当会有被盗USDT风险💀 苹果用户下载教程如下! 1:把苹果应用市场的ID修改成国外ID 2:直接搜索 欧易 进行下载

17 Feb 2024, 16:40 UTC≈5,400 viewsread 15 August 2026

苹果担保对应规则: #公群交易规则 #担保公群收费标准 #下押标准 #公群罚款标准 #公群运营规则 以下公群交易规则以及收费标准跟罚款标准及下押标准及公群运营规则,凡与我方所有产生交易默认已读并确认,出现问题后果自负! 一、担保公群收费及下押标准 1.公群上押金额500u起,跑分 代收代付 手机口 游戏赌博等项目800u起押,具体上押金额根据项目风险来确定。 2.无上押下押费用,只收取每月管理费百分之5,无其它任何费用! 3.公群无纠纷且无交易条件下可联系负责人申请退押,退押后需要等待24H,在24H内无任何纠纷财务会立即打款退押! 4.公群更换项目,如在公群原基础修改项目不收费,修改项目加发布公群列表收费10u。 5.收费业务打款后如您不需要此业务,我们的收费将不退款! 二、公群交易规则 1.做单前先看好群规,问好规则,严格按照公群要求及规则做单,如有纠纷我们按照公群规则宣判。 2.在进公群单线群对接之前请先联系苹果

17 Feb 2024, 16:08 UTC≈3,840 viewsread 15 August 2026

-⚒苹果担保自助服务中心⚙️- 👨‍✈️ 苹果唯一负责人:@pgdb 🤣官方广告地址: 🤣官方上押地址: 🔍查找以上压公群🔍 (负责人不是群管理的均为假押) 🤣所有公群查询🤣 😂供需频道 😂欧易下载 😂公群规则 😂上压规则 😂上压联系 😂人工发布 😂官方中文包 😂官方群管 😂查U记账 😂福利抽奖 😂腾讯视频 😂网易音乐 🤣TG 官 方 高 速 代 理🤣 🤣全 球 华 人 交 流 群🤣

Showing the 5 most recent of 5 posts we hold for @pgdb. 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.

Citation-graph rank

Citation-graph rank — 1,601,161 of 1,625,954entries 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 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“苹果担保公群导航 @PGDB” (@pgdb), 195 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/pgdb.

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.