Bot

中国担保验群机器人 @ZGDB

@JYMBOT

On this record: Growth · Engagement · Cite this entry

36,198monthly users

+2,686 since we began measuring on 14 August 2026

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

Register entry

Telegram ID	5096679265
Type	Bot
Username	@JYMBOT
First recorded	14 August 2026
Last confirmed live	30 August 2026
Measurements held	7
Confirmed unchanged	1 time, most recently 30 August 2026
On Telegram	t.me/JYMBOT

Growth

7 measurements spanning 16 days, net +2,686. 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 31,469–36,815 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
30 Aug 2026, 18:55	36,198	+118
27 Aug 2026, 18:16	36,080	+758
23 Aug 2026, 13:27	35,322	+2,069
20 Aug 2026, 16:26	33,253	+440
17 Aug 2026, 15:46	32,813	+727
16 Aug 2026, 06:23	32,086	-1,426
14 Aug 2026, 19:08	33,512	first 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.

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

“中国担保验群机器人 @ZGDB” (@JYMBOT), 36,198 monthly users as measured 30 August 2026. Telegram Register, tgregister.com/channel/JYMBOT.

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.