Channel
@tgdbgq
On this record: Growth · Engagement · Posts · Citations · Cite this entry
34,551subscribers
-77 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| 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 | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/tgdbgq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 11:59 | 34,551 | no change |
| 13 Aug 2026, 08:48 | 34,551 | -43 |
| 13 Aug 2026, 08:04 | 34,594 | -18 |
| 12 Aug 2026, 13:17 | 34,612 | no change |
| 12 Aug 2026, 08:53 | 34,612 | -16 |
| 12 Aug 2026, 05:00 | 34,628 | no change |
| 12 Aug 2026, 04:47 | 34,628 | first reading |
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 4 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (25 May 2026 – 5 August 2026) |
| Views total | 3,240 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 05:08 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.
所有公群均已退押 @guanfang1 @guanfang2 @guanfang3 @guanfang4 @guanfang5 @guanfang6 @guanfang7 @guanfang8 @guanfang9 官方1-9全拼 @tgdanbao 已升级机器人 @danbaotg @app1 @app2 @tgpaofen VIP群一个 担保打包出售 可单个出售 价格私聊 @guanfang1
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.
Citation-graph rank — 278,874 of 1,169,250entries 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 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“TG担保公群@app1” (@tgdbgq), 34,551 subscribers as measured 13 August 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.