Telegram RegisterThe public register of Telegram
Telegram profile photo for QG担保 频道社区

Channel

QG担保 频道社区

@QGDBPD

On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

10,165subscribers

+50 since we began measuring on 20 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002342209536
TypeChannel
Username@QGDBPD
Created8 October 2024measured — dated from the channel’s first post
First recorded20 August 2026
Last confirmed live6 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/QGDBPD

Growth

10,11510,16510,14020 August 2026 — 10,115 subscribers20 August 2026 — 10,119 subscribers22 August 2026 — 10,129 subscribers24 August 2026 — 10,136 subscribers25 August 2026 — 10,137 subscribers26 August 2026 — 10,140 subscribers27 August 2026 — 10,148 subscribers28 August 2026 — 10,150 subscribers29 August 2026 — 10,152 subscribers30 August 2026 — 10,153 subscribers31 August 2026 — 10,154 subscribers1 September 2026 — 10,159 subscribers2 September 2026 — 10,161 subscribers4 September 2026 — 10,164 subscribers6 September 2026 — 10,165 subscribers20 August 20266 September 2026
15 measurements spanning 17 days, net +50. 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 10,108–10,173 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 12:1610,165+1
4 Sept 2026, 05:2110,164+3
2 Sept 2026, 18:2610,161+2
1 Sept 2026, 17:0410,159+5
31 Aug 2026, 14:1310,154+1
30 Aug 2026, 15:5410,153+1
29 Aug 2026, 17:4310,152+2
28 Aug 2026, 14:3210,150+2
27 Aug 2026, 13:1510,148+8
26 Aug 2026, 16:1210,140+3
25 Aug 2026, 12:4510,137+1
24 Aug 2026, 10:3410,136+7
22 Aug 2026, 18:4410,129+10
20 Aug 2026, 11:1310,119+4
20 Aug 2026, 06:0010,115first reading

Engagement

4 posts held, back to 8 October 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 16 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
39.1%
avg views ÷ 10,165 subscribers
Avg views / post
3,980
2 posts measured
Reaction rate
0.013%
reactions ÷ views · ER floor
Posts in window
3
of 4 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. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held4 (8 October 202414 August 2026)
Views total7,956
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 03:45 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 4 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 4 most recent posts we hold, published 8 October 2024 to 14 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

14 Aug 2026, 10:31 UTC≈7,610 views1 reactionsread 29 August 2026

QG担保在押公群列表 01 QG公群 入口 3000U 02 QG公群 入口 3000U 03 QG公群 入口 3000U 04 QG公群 入口 3000U QG担保官方大群 https://t.me/QGDBDQ QG担保负责人如下 @QYQYBA @QGDBGG

1

10 Aug 2026, 12:36 UTCviews —

QG担保 频道社区 pinned «QG担保官方人员核验中心 担保专员:@QGDBGG 担保负责人:@QYQYBA 本页面未列出的任何账号均不得代表官方。 重要备注说明: 1、以上述 群组、频道、人员、均属于『QG担保 』持有,认准认清,谨防冒充、如有被骗 本担保方不承担任何责任; 2、仔细核对我们的担保交易地址,线上上押目前只收 USDT ,不收RMB,使用其他账户和地址的都是骗子; 3、担保人员不会主动私聊以及发送地址和任何交易; 4、辨别我们担保方真假小技巧,从担保导航点入,稍微仔细阅读,添加备注; 骗子常用伎俩: 1、抄袭使用官方头像、昵称、简介;…»

10 Aug 2026, 12:36 UTC346 viewsread 29 August 2026

QG担保官方人员核验中心 担保专员:@QGDBGG 担保负责人:@QYQYBA 本页面未列出的任何账号均不得代表官方。 重要备注说明: 1、以上述 群组、频道、人员、均属于『QG担保 』持有,认准认清,谨防冒充、如有被骗 本担保方不承担任何责任; 2、仔细核对我们的担保交易地址,线上上押目前只收 USDT ,不收RMB,使用其他账户和地址的都是骗子; 3、担保人员不会主动私聊以及发送地址和任何交易; 4、辨别我们担保方真假小技巧,从担保导航点入,稍微仔细阅读,添加备注; 骗子常用伎俩: 1、抄袭使用官方头像、昵称、简介; 2、使用特殊字符模仿官方用户名,如:大写i、小写L、字母O、数字0等; 3、抄袭头像、昵称、简介,不显示电话号码或用户名; 4、抄袭头像、昵称,将电话号码或用户名写入简介栏。

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

@QGDBPD 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
20 August 2026
Most recent edit
22 August 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“QG担保 频道社区” (@QGDBPD), 10,165 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/QGDBPD.

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.