Telegram RegisterThe public register of Telegram
Telegram profile photo for TRON China

Supergroup

TRON China

@tronnetworkCN

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

9,224members

+478 since we began measuring on 6 August 2026

39 online right now

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

Register entry

Telegram ID-1001340179566
TypeSupergroup
Username@tronnetworkCN
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live20 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 20 October 2026
On Telegramt.me/tronnetworkCN

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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

8,7469,2248,9856 August 2026 — 8,746 members6 August 2026 — 8,748 members9 August 2026 — 8,795 members12 August 2026 — 8,819 members15 August 2026 — 8,864 members18 August 2026 — 8,888 members22 August 2026 — 8,932 members24 August 2026 — 8,932 members25 August 2026 — 8,931 members28 August 2026 — 8,927 members31 August 2026 — 8,933 members3 September 2026 — 8,920 members9 September 2026 — 8,891 members13 September 2026 — 8,861 members17 September 2026 — 8,893 members25 September 2026 — 8,900 members4 October 2026 — 9,024 members10 October 2026 — 9,106 members14 October 2026 — 9,151 members16 October 2026 — 9,182 members20 October 2026 — 9,224 members6 August 202620 October 2026
21 measurements spanning 75 days, net +478. 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 8,674–9,296 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 21
Measured (UTC)MembersChange
20 Oct 2026, 02:319,224+42
16 Oct 2026, 22:149,182+31
14 Oct 2026, 08:269,151+45
10 Oct 2026, 17:209,106+82
4 Oct 2026, 20:429,024+124
25 Sept 2026, 05:588,900+7
17 Sept 2026, 07:588,893+32
13 Sept 2026, 09:568,861-30
9 Sept 2026, 09:218,891-29
3 Sept 2026, 22:218,920-13
31 Aug 2026, 18:048,933+6
28 Aug 2026, 13:348,927-4
25 Aug 2026, 14:348,931-1
24 Aug 2026, 11:088,932no change
22 Aug 2026, 06:368,932+44
18 Aug 2026, 15:258,888+24
15 Aug 2026, 19:288,864+45
12 Aug 2026, 07:478,819+24
9 Aug 2026, 05:038,795+47
6 Aug 2026, 14:448,748first reading

Engagement

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

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

“TRON China” (@tronnetworkCN), 9,224 members as measured 20 October 2026. Telegram Register, tgregister.com/channel/tronnetworkCN.

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.