Telegram RegisterThe public register of Telegram
Telegram profile photo for 天津意风教学助手

Bot

天津意风教学助手

@tianjinXZ_bot

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

28,820monthly users

+5,724 since we began measuring on 17 August 2026

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

Register entry

Telegram ID7836701999
TypeBot
Username@tianjinXZ_bot
First recorded17 August 2026
Last confirmed live7 November 2026
Measurements held37
Confirmed unchanged2 times, most recently 7 November 2026
On Telegramt.me/tianjinXZ_bot

Topic

Education — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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

23,09632,62027,85817 August 2026 — 23,096 monthly users18 August 2026 — 31,174 monthly users19 August 2026 — 32,095 monthly users22 August 2026 — 31,907 monthly users24 August 2026 — 32,241 monthly users25 August 2026 — 31,975 monthly users26 August 2026 — 32,313 monthly users28 August 2026 — 32,293 monthly users29 August 2026 — 32,352 monthly users31 August 2026 — 32,131 monthly users2 September 2026 — 32,466 monthly users6 September 2026 — 32,467 monthly users9 September 2026 — 32,332 monthly users12 September 2026 — 31,366 monthly users13 September 2026 — 28,877 monthly users15 September 2026 — 30,497 monthly users19 September 2026 — 28,493 monthly users26 September 2026 — 31,518 monthly users4 October 2026 — 32,287 monthly users8 October 2026 — 32,515 monthly users13 October 2026 — 32,620 monthly users14 October 2026 — 32,571 monthly users15 October 2026 — 32,574 monthly users16 October 2026 — 31,857 monthly users18 October 2026 — 31,894 monthly users20 October 2026 — 29,530 monthly users22 October 2026 — 26,501 monthly users23 October 2026 — 29,507 monthly users25 October 2026 — 29,183 monthly users26 October 2026 — 28,918 monthly users27 October 2026 — 28,912 monthly users29 October 2026 — 28,664 monthly users30 October 2026 — 28,936 monthly users1 November 2026 — 28,929 monthly users2 November 2026 — 28,901 monthly users4 November 2026 — 28,891 monthly users6 November 2026 — 28,820 monthly users28,82017 August 20266 November 2026
37 measurements spanning 81 days, net +5,724. 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 21,667–34,049 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 37
Measured (UTC)Monthly usersChange
6 Nov 2026, 20:4628,820-71
4 Nov 2026, 19:2528,891-10
2 Nov 2026, 15:2928,901-28
1 Nov 2026, 12:5928,929-7
30 Oct 2026, 15:1528,936+272
29 Oct 2026, 13:1528,664-248
27 Oct 2026, 07:4128,912-6
26 Oct 2026, 07:3028,918-265
25 Oct 2026, 04:4729,183-324
23 Oct 2026, 03:2029,507+3,006
22 Oct 2026, 04:2026,501-3,029
20 Oct 2026, 23:2729,530-2,364
18 Oct 2026, 21:2831,894+37
16 Oct 2026, 18:2831,857-717
15 Oct 2026, 19:4932,574+3
14 Oct 2026, 16:2832,571-49
13 Oct 2026, 03:1632,620+105
8 Oct 2026, 22:3932,515+228
4 Oct 2026, 15:3832,287+769
26 Sept 2026, 14:4031,518first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“天津意风教学助手” (@tianjinXZ_bot), 28,820 monthly users as measured 6 November 2026. Telegram Register, tgregister.com/channel/tianjinXZ_bot.

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.