Telegram RegisterThe public register of Telegram
Telegram profile photo for 新币公群 @xbqqg

Channel

新币公群 @xbqqg

@xbqqg

7 usernames

On this record: Topic · Growth · Engagement · Citations · Cite this entry

429,176subscribers

-651 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1002310895574
TypeChannel
Usernames@badb88 @danbao226 @gongqun68 @gqdh66 @kefu569 @xbdb626 @xbqqg
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live9 September 2026
Measurements held43
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/xbqqg

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 13 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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 why it has no browse page of its own yet.

Growth

419,975438,770429,372.513 August 2026 — 429,827 subscribers13 August 2026 — 429,827 subscribers14 August 2026 — 429,021 subscribers14 August 2026 — 428,994 subscribers16 August 2026 — 433,055 subscribers16 August 2026 — 433,010 subscribers17 August 2026 — 428,792 subscribers17 August 2026 — 428,667 subscribers18 August 2026 — 427,824 subscribers18 August 2026 — 427,768 subscribers19 August 2026 — 425,189 subscribers19 August 2026 — 425,061 subscribers20 August 2026 — 423,927 subscribers20 August 2026 — 420,499 subscribers21 August 2026 — 420,111 subscribers21 August 2026 — 419,975 subscribers22 August 2026 — 422,387 subscribers23 August 2026 — 438,770 subscribers24 August 2026 — 436,216 subscribers24 August 2026 — 435,117 subscribers25 August 2026 — 433,582 subscribers25 August 2026 — 436,400 subscribers26 August 2026 — 436,005 subscribers26 August 2026 — 435,208 subscribers27 August 2026 — 433,510 subscribers27 August 2026 — 431,881 subscribers28 August 2026 — 431,571 subscribers28 August 2026 — 430,623 subscribers29 August 2026 — 430,236 subscribers30 August 2026 — 429,218 subscribers30 August 2026 — 428,840 subscribers31 August 2026 — 431,661 subscribers31 August 2026 — 431,485 subscribers1 September 2026 — 430,567 subscribers1 September 2026 — 429,965 subscribers1 September 2026 — 428,988 subscribers2 September 2026 — 433,357 subscribers3 September 2026 — 433,677 subscribers3 September 2026 — 436,436 subscribers4 September 2026 — 435,648 subscribers5 September 2026 — 434,632 subscribers7 September 2026 — 431,833 subscribers9 September 2026 — 429,176 subscribers429,17613 August 20269 September 2026
43 measurements spanning 27 days, net -651. 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 417,156–441,589 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
9 Sept 2026, 06:17429,176-2,657
7 Sept 2026, 08:37431,833-2,799
5 Sept 2026, 20:21434,632-1,016
4 Sept 2026, 13:59435,648-788
3 Sept 2026, 16:59436,436+2,759
3 Sept 2026, 01:46433,677+320
2 Sept 2026, 12:54433,357+4,369
1 Sept 2026, 22:57428,988-977
1 Sept 2026, 10:47429,965-602
1 Sept 2026, 00:25430,567-918
31 Aug 2026, 11:25431,485-176
31 Aug 2026, 03:04431,661+2,821
30 Aug 2026, 12:48428,840-378
30 Aug 2026, 00:16429,218-1,018
29 Aug 2026, 10:13430,236-387
28 Aug 2026, 21:45430,623-948
28 Aug 2026, 11:06431,571-310
27 Aug 2026, 22:44431,881-1,629
27 Aug 2026, 11:38433,510-1,698
26 Aug 2026, 23:25435,208first reading

Engagement

No public post preview. We read this entry on 13 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 4 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.

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

“新币公群 @xbqqg” (@xbqqg), 429,176 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/xbqqg.

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.