Bot

Mapp.kz

@MappKZ_BOT

On this record: Growth · Engagement · Cite this entry

14,848monthly users

+332 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 ID	7332714405
Type	Bot
Username	@MappKZ_BOT
First recorded	19 August 2026
Last confirmed live	27 August 2026
Measurements held	8
Confirmed unchanged	4 times, most recently 27 August 2026
On Telegram	t.me/MappKZ_BOT

Growth

8 measurements spanning 17 days, net +332. 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 13,805–14,984 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
24 Aug 2026, 19:07	14,848	+16
21 Aug 2026, 15:26	14,832	+648
19 Aug 2026, 10:43	14,184	no change
18 Aug 2026, 10:04	14,184	+243
15 Aug 2026, 17:26	13,941	-374
11 Aug 2026, 22:58	14,315	+19
10 Aug 2026, 20:43	14,296	-220
7 Aug 2026, 21:59	14,516	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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“Mapp.kz” (@MappKZ_BOT), 14,848 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/MappKZ_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.