Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐Ÿ™‹๐Ÿปโ€โ™€๏ธ่ต„ๆบๆ˜“ๆŸฅ่ฏข

Bot

๐Ÿ™‹๐Ÿปโ€โ™€๏ธ่ต„ๆบๆ˜“ๆŸฅ่ฏข

@XiaomengGroupBot

On this record: Topic ยท Growth ยท Engagement ยท Citations ยท Cite this entry

25,683monthly users

+9,017 since we began measuring on 8 August 2026

Risers and fallers across the register ยท movement among entries of 10,000โ€“31,623.

Register entry

Telegram ID8780307017
TypeBot
Username@XiaomengGroupBot
First recorded17 August 2026
Last confirmed live7 November 2026
Measurements held37
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/XiaomengGroupBot

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

16,66633,72125,193.58 August 2026 โ€” 16,666 monthly users10 August 2026 โ€” 16,881 monthly users12 August 2026 โ€” 17,042 monthly users14 August 2026 โ€” 17,198 monthly users17 August 2026 โ€” 17,416 monthly users17 August 2026 โ€” 17,416 monthly users20 August 2026 โ€” 17,533 monthly users22 August 2026 โ€” 17,534 monthly users23 August 2026 โ€” 17,609 monthly users25 August 2026 โ€” 17,832 monthly users27 August 2026 โ€” 17,959 monthly users28 August 2026 โ€” 17,666 monthly users29 August 2026 โ€” 18,210 monthly users1 September 2026 โ€” 18,123 monthly users5 September 2026 โ€” 18,658 monthly users8 September 2026 โ€” 23,182 monthly users11 September 2026 โ€” 28,906 monthly users13 September 2026 โ€” 29,068 monthly users17 September 2026 โ€” 28,794 monthly users19 September 2026 โ€” 29,340 monthly users27 September 2026 โ€” 33,721 monthly users4 October 2026 โ€” 33,498 monthly users9 October 2026 โ€” 32,341 monthly users13 October 2026 โ€” 28,849 monthly users14 October 2026 โ€” 23,531 monthly users15 October 2026 โ€” 23,486 monthly users17 October 2026 โ€” 23,443 monthly users21 October 2026 โ€” 26,709 monthly users23 October 2026 โ€” 22,176 monthly users26 October 2026 โ€” 22,248 monthly users28 October 2026 โ€” 22,431 monthly users29 October 2026 โ€” 25,586 monthly users31 October 2026 โ€” 25,527 monthly users1 November 2026 โ€” 25,613 monthly users3 November 2026 โ€” 25,203 monthly users5 November 2026 โ€” 25,739 monthly users7 November 2026 โ€” 25,683 monthly users25,6838 August 20267 November 2026
37 measurements spanning 91 days, net +9,017. 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 14,108โ€“36,279 and does not start at zero.
Measurement log โ€” every monthly users count we have recorded, most recent 20 of 37
Measured (UTC)Monthly usersChange
7 Nov 2026, 12:4925,683-56
5 Nov 2026, 18:2625,739+536
3 Nov 2026, 18:2725,203-410
1 Nov 2026, 13:4825,613+86
31 Oct 2026, 12:4425,527-59
29 Oct 2026, 09:4025,586+3,155
28 Oct 2026, 07:4722,431+183
26 Oct 2026, 11:0622,248+72
23 Oct 2026, 08:5022,176-4,533
21 Oct 2026, 08:1626,709+3,266
17 Oct 2026, 13:2023,443-43
15 Oct 2026, 15:4023,486-45
14 Oct 2026, 18:5823,531-5,318
13 Oct 2026, 10:5128,849-3,492
9 Oct 2026, 07:5632,341-1,157
4 Oct 2026, 19:1533,498-223
27 Sept 2026, 01:3533,721+4,381
19 Sept 2026, 17:3729,340+546
17 Sept 2026, 03:4028,794-274
13 Sept 2026, 09:5829,068first 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

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 9 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 7 November 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐Ÿ™‹๐Ÿปโ€โ™€๏ธ่ต„ๆบๆ˜“ๆŸฅ่ฏขโ€ (@XiaomengGroupBot), 25,683 monthly users as measured 7 November 2026. Telegram Register, tgregister.com/channel/XiaomengGroupBot.

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.