Telegram RegisterThe public register of Telegram
Telegram profile photo for 青年文摘

Channel

青年文摘

@bjgroupqnwz

2 usernames

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

5,988subscribers

-32 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001524876231
TypeChannel
Usernames@bjgroupqnwz @Bjgroupwz
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live5 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/bjgroupqnwz

Growth

5,9846,0216,002.57 August 2026 — 6,020 subscribers7 August 2026 — 6,021 subscribers10 August 2026 — 6,019 subscribers14 August 2026 — 6,014 subscribers17 August 2026 — 5,997 subscribers20 August 2026 — 6,000 subscribers24 August 2026 — 5,995 subscribers28 August 2026 — 5,993 subscribers29 August 2026 — 5,993 subscribers30 August 2026 — 5,986 subscribers30 August 2026 — 5,989 subscribers1 September 2026 — 5,987 subscribers2 September 2026 — 5,984 subscribers5 September 2026 — 5,988 subscribers5,9887 August 20265 September 2026
14 measurements spanning 29 days, net -32. 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 5,978–6,027 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 11:375,988+4
2 Sept 2026, 19:275,984-3
1 Sept 2026, 15:575,987-2
30 Aug 2026, 20:535,989+3
30 Aug 2026, 00:145,986-7
29 Aug 2026, 21:085,993no change
28 Aug 2026, 01:145,993-2
24 Aug 2026, 15:135,995-5
20 Aug 2026, 23:126,000+3
17 Aug 2026, 16:555,997-17
14 Aug 2026, 03:086,014-5
10 Aug 2026, 14:436,019-2
7 Aug 2026, 17:466,021+1
7 Aug 2026, 08:476,020first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Mentions

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

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

“青年文摘” (@bjgroupqnwz), 5,988 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/bjgroupqnwz.

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.