Telegram RegisterThe public register of Telegram
Telegram profile photo for Z16 Service

Bot

Z16 Service

@z16service_bot

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

13,859monthly users

+1,040 since we began measuring on 7 August 2026

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

Register entry

Telegram ID7245733579
TypeBot
Username@z16service_bot
First recorded19 August 2026
Last confirmed live27 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/z16service_bot

Growth

12,81914,09613,457.57 August 2026 — 12,819 monthly users8 August 2026 — 13,143 monthly users10 August 2026 — 12,923 monthly users12 August 2026 — 13,442 monthly users17 August 2026 — 13,670 monthly users18 August 2026 — 13,608 monthly users19 August 2026 — 13,608 monthly users20 August 2026 — 13,979 monthly users24 August 2026 — 14,096 monthly users27 August 2026 — 13,859 monthly users13,8597 August 202627 August 2026
10 measurements spanning 20 days, net +1,040. 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 12,627–14,288 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
27 Aug 2026, 00:5613,859-237
24 Aug 2026, 19:3714,096+117
20 Aug 2026, 19:0213,979+371
19 Aug 2026, 19:5513,608no change
18 Aug 2026, 14:2413,608-62
17 Aug 2026, 11:1713,670+228
12 Aug 2026, 22:1713,442+519
10 Aug 2026, 23:4512,923-220
8 Aug 2026, 22:2113,143+324
7 Aug 2026, 10:1512,819first 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.

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

“Z16 Service” (@z16service_bot), 13,859 monthly users as measured 27 August 2026. Telegram Register, tgregister.com/channel/z16service_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.