Channel
Channel Komunitas zhuan
@zhuancommunity
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,927subscribers
+16 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 | -1001728684483 |
|---|---|
| Type | Channel |
| Username | @zhuancommunity |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/zhuancommunity |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 04:22 | 3,927 | +3 |
| 13 Sept 2026, 19:37 | 3,924 | -4 |
| 10 Sept 2026, 09:19 | 3,928 | +3 |
| 5 Sept 2026, 23:20 | 3,925 | no change |
| 5 Sept 2026, 00:21 | 3,925 | -3 |
| 1 Sept 2026, 06:38 | 3,928 | +9 |
| 29 Aug 2026, 05:56 | 3,919 | +4 |
| 26 Aug 2026, 10:56 | 3,915 | +4 |
| 23 Aug 2026, 12:09 | 3,911 | -2 |
| 20 Aug 2026, 08:24 | 3,913 | +1 |
| 17 Aug 2026, 17:48 | 3,912 | +2 |
| 14 Aug 2026, 11:45 | 3,910 | +1 |
| 11 Aug 2026, 06:05 | 3,909 | -2 |
| 7 Aug 2026, 17:41 | 3,911 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@Idxtradingcomm · 53,199
Telegram ranks this channel #12 of 87 here — alongside 86 others — read 27 August 2026
@sahamsuksesberkah01 · 30,603
Telegram ranks this channel #21 of 75 here — alongside 74 others — read 7 September 2026
@wigunainvestment · 53,394
Telegram ranks this channel #34 of 91 here — alongside 90 others — read 27 August 2026
@creativetrader · 41,294
Telegram ranks this channel #55 of 80 here — alongside 79 others — read 29 August 2026
@phintasprofits · 22,954
Telegram ranks this channel #74 of 76 here — alongside 75 others — read 19 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Channel Komunitas zhuan” (@zhuancommunity), 3,927 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/zhuancommunity.
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.