Telegram RegisterThe public register of Telegram
Telegram profile photo for 公群D组-3688 金六福白资承兑-七天担保-9700U(晴空)

Supergroup

公群D组-3688 金六福白资承兑-七天担保-9700U(晴空)

@qtdb_3688

2 usernames

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

10,671members

+3,910 since we began measuring on 7 August 2026

30 online right now

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

Register entry

Telegram ID-1002055944177
TypeSupergroup
Usernames@Chinajisou1 @qtdb_3688
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live16 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/qtdb_3688

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.

Growth

1711,5745,795.57 August 2026 — 6,761 members8 August 2026 — 6,759 members10 August 2026 — 6,881 members14 August 2026 — 6,934 members17 August 2026 — 7,124 members20 August 2026 — 7,696 members24 August 2026 — 8,105 members25 August 2026 — 8,105 members27 August 2026 — 8,932 members30 August 2026 — 8,885 members2 September 2026 — 9,351 members9 September 2026 — 17 members12 September 2026 — 9,644 members13 September 2026 — 9,667 members17 September 2026 — 99 members18 September 2026 — 10,031 members30 September 2026 — 220 members2 October 2026 — 11,167 members7 October 2026 — 11,176 members12 October 2026 — 11,419 members12 October 2026 — 317 members14 October 2026 — 11,364 members15 October 2026 — 11,392 members16 October 2026 — 11,490 members17 October 2026 — 11,489 members18 October 2026 — 11,508 members19 October 2026 — 11,574 members20 October 2026 — 404 members20 October 2026 — 11,538 members21 October 2026 — 11,493 members22 October 2026 — 11,366 members24 October 2026 — 11,316 members25 October 2026 — 11,283 members26 October 2026 — 11,263 members27 October 2026 — 484 members27 October 2026 — 11,246 members28 October 2026 — 11,136 members29 October 2026 — 11,114 members30 October 2026 — 11,065 members31 October 2026 — 11,080 members1 November 2026 — 10,993 members2 November 2026 — 546 members2 November 2026 — 11,047 members3 November 2026 — 11,030 members4 November 2026 — 11,044 members5 November 2026 — 11,101 members6 November 2026 — 11,124 members7 November 2026 — 10,896 members8 November 2026 — 10,823 members9 November 2026 — 608 members10 November 2026 — 10,717 members12 November 2026 — 10,690 members16 November 2026 — 10,671 members10,6717 August 202616 November 2026
53 measurements spanning 101 days, net +3,910. 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”.
Measurement log — every members count we have recorded, most recent 20 of 53
Measured (UTC)MembersChange
16 Nov 2026, 03:4010,671-19
12 Nov 2026, 14:1610,690-27
10 Nov 2026, 08:4110,717+10,109
9 Nov 2026, 14:46608-10,215
8 Nov 2026, 19:2010,823-73
7 Nov 2026, 11:3110,896-228
6 Nov 2026, 12:0711,124+23
5 Nov 2026, 11:3611,101+57
4 Nov 2026, 12:5511,044+14
3 Nov 2026, 15:4611,030-17
2 Nov 2026, 14:5711,047+10,501
2 Nov 2026, 14:38546-10,447
1 Nov 2026, 12:5610,993-87
31 Oct 2026, 13:0011,080+15
30 Oct 2026, 16:0611,065-49
29 Oct 2026, 14:4611,114-22
28 Oct 2026, 10:4511,136-110
27 Oct 2026, 09:1611,246+10,762
27 Oct 2026, 01:59484-10,779
26 Oct 2026, 11:2611,263first reading

Engagement

No public post preview. We read this entry on 3 November 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 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.

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

“公群D组-3688 金六福白资承兑-七天担保-9700U(晴空)” (@qtdb_3688), 10,671 members as measured 16 November 2026. Telegram Register, tgregister.com/channel/qtdb_3688.

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.