所有公群均已退押 @guanfang1 @guanfang2 @guanfang3 @guanfang4 @guanfang5 @guanfang6 @guanfang7 @guanfang8 @guanfang9 官方1-9全拼 @tgdanbao 已升级机器人 @danbaotg @app1 @app2 @tgpaofen VIP群一个 担保打包出售 可单个出售 价格私聊 @guanfang1

Channel
TG担保公群@app1
@tgdbgq
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
25,809subscribers
-8,819 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002408155409 |
|---|---|
| Type | Channel |
| Usernames | @guanfang4 @guanfang6 @tgdbgq |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/tgdbgq |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 06:55 | 25,809 | no change |
| 8 Sept 2026, 05:21 | 25,809 | -408 |
| 7 Sept 2026, 00:58 | 26,217 | -857 |
| 5 Sept 2026, 03:22 | 27,074 | no change |
| 4 Sept 2026, 23:58 | 27,074 | -443 |
| 4 Sept 2026, 07:57 | 27,517 | -430 |
| 3 Sept 2026, 09:03 | 27,947 | no change |
| 3 Sept 2026, 06:09 | 27,947 | -68 |
| 2 Sept 2026, 20:49 | 28,015 | -422 |
| 2 Sept 2026, 03:45 | 28,437 | no change |
| 2 Sept 2026, 02:05 | 28,437 | -88 |
| 1 Sept 2026, 19:48 | 28,525 | -499 |
| 1 Sept 2026, 02:45 | 29,024 | no change |
| 1 Sept 2026, 00:07 | 29,024 | -303 |
| 31 Aug 2026, 18:18 | 29,327 | -193 |
| 31 Aug 2026, 05:04 | 29,520 | -193 |
| 30 Aug 2026, 20:13 | 29,713 | no change |
| 30 Aug 2026, 17:38 | 29,713 | -199 |
| 30 Aug 2026, 04:04 | 29,912 | -352 |
| 29 Aug 2026, 19:04 | 30,264 | first reading |
Engagement
20 posts held, back to 25 May 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 46 pages 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
TG担保公群@app1 pinned «尊敬的各位用户、合作伙伴: 感谢大家一直以来对本平台的支持与信任。 经过团队长期评估与慎重决定,本平台将于2026年8月4日起正式停止 Telegram 担保业务运营。 市场混乱小担保频繁跑路,市场改革变迁,现阶段进行停运处理。 在此期间: 已进行中的订单将按照规则正常处理; 用户相关事项请提前联系官方客服进行确认; 停止运营后,将不再接受新的业务申请。 各位公群商户和专群商户联系 @guanfang1 进行退押手续处理 一路走来,我们感谢每一位用户、合作伙伴给予的认可与支持。过去的每一次合作,都是我们不断前进的动力。…»
尊敬的各位用户、合作伙伴: 感谢大家一直以来对本平台的支持与信任。 经过团队长期评估与慎重决定,本平台将于2026年8月4日起正式停止 Telegram 担保业务运营。 市场混乱小担保频繁跑路,市场改革变迁,现阶段进行停运处理。 在此期间: 已进行中的订单将按照规则正常处理; 用户相关事项请提前联系官方客服进行确认; 停止运营后,将不再接受新的业务申请。 各位公群商户和专群商户联系 @guanfang1 进行退押手续处理 一路走来,我们感谢每一位用户、合作伙伴给予的认可与支持。过去的每一次合作,都是我们不断前进的动力。 江湖路远,感谢相遇。 特此公告。
⚡️ 上押客服 @guanfang1 🤖 双向联系 @TGdanbao 😃TG供需 @app2 😃新群播报 @TGxinqun 👉不用到处找!一键收藏TG担保 点不开的需把TG升级至最高版本👈
①代收付公群: 1.一道卡接回u 2.码接回u 3.二道卡接回u 4.app跑分 5.救火卡扣 6.NFC远程刷卡 7.欠款代还 ②承兑公群: 1.现金业务 2.三方承兑 3.POS承兑 4.实物承兑 5.礼品卡 6.平台币核销 ③白资公群: 1.白资收u代付 2.白资收u出u 3.海外白资代付 ④招商合作窗口: 1.招车队/招料主 2.招聊手/后续代打 3.包养窗口 4.跟车承兑 5.彩票/六合彩内幕/蛇货协议球 ⑤引流类: 1.手机口/接听口/短信口/快手口 2.电销 3.短信代发 4.拉手/话术单 5.视频代发 6.收粉/出粉 7.租各种号 8.TG引流 ⑥买卖类: 1.各种账号 2.手机卡 3.TG号/会员/NFT/888匿名号 4.TRX能量与兑换 5.烟酒/保健品/奢侈品 6.其他买卖 ⑦服务类: 1.天眼查 2.票务代付 3.美工设计 4.接码注册实名账号 5.代办/代打电话 6.高端外围 7.苹果ID…
其他娱乐 (注意:不在此导航里面的群都是假公群,必须在公群内交易, 我们只担保公群内的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负, 不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息, 涉及个人隐私的可以部分以星号代替,并私聊发完整的。) 第1页
德州扑克 (注意:不在此导航里面的群都是假公群,必须在公群内交易, 我们只担保公群内的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负, 不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息, 涉及个人隐私的可以部分以星号代替,并私聊发完整的。) 第1页
综合盘/电子 (注意:不在此导航里面的群都是假公群,必须在公群内交易, 我们只担保公群内的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负, 不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息, 涉及个人隐私的可以部分以星号代替,并私聊发完整的。) 第1页
骰子 (注意:不在此导航里面的群都是假公群,必须在公群内交易, 我们只担保公群内的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负, 不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息, 涉及个人隐私的可以部分以星号代替,并私聊发完整的。) 第1页
备用消息
备用消息
PC20/PC28/PC网盘 (注意:不在此导航里面的群都是假公群,必须在公群内交易, 我们只担保公群内的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负, 不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息, 涉及个人隐私的可以部分以星号代替,并私聊发完整的。) 第1页
Showing the 12 most recent of 20 posts we hold for @tgdbgq. 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 3 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@tgdbgq named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 5 posts, 14 August 2026 – 26 August 2026
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“TG担保公群@app1” (@tgdbgq), 25,809 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/tgdbgq.
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.