Telegram RegisterThe public register of Telegram

Bot

@ASPNKENIKMATANKU

@ASPNKENIKMATAN_BOT

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

44,757monthly users

-1,669 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8378587437
TypeBot
Username@ASPNKENIKMATAN_BOT
First recorded12 August 2026
Last confirmed live26 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/ASPNKENIKMATAN_BOT

Previous handles

@ASPNKENIKMATAN_BOT was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@ASPNKENIKMATAN_BOT
held 12 August 202612 August 2026

Growth

43,40846,42644,9177 August 2026 — 46,426 monthly users8 August 2026 — 46,111 monthly users11 August 2026 — 44,526 monthly users12 August 2026 — 44,526 monthly users13 August 2026 — 44,983 monthly users16 August 2026 — 43,408 monthly users18 August 2026 — 43,695 monthly users20 August 2026 — 43,709 monthly users23 August 2026 — 43,944 monthly users24 August 2026 — 44,298 monthly users26 August 2026 — 44,757 monthly users44,7577 August 202626 August 2026
11 measurements spanning 19 days, net -1,669. 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 42,955–46,879 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Aug 2026, 20:0444,757+459
24 Aug 2026, 19:3244,298+354
23 Aug 2026, 03:0443,944+235
20 Aug 2026, 13:1643,709+14
18 Aug 2026, 17:2243,695+287
16 Aug 2026, 04:5643,408-1,575
13 Aug 2026, 07:2944,983+457
12 Aug 2026, 19:0844,526no change
11 Aug 2026, 08:4644,526-1,585
8 Aug 2026, 00:2746,111-315
7 Aug 2026, 19:0146,426first 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 3 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 26 August 2026 — this entry's latest reading, not the date you are reading this.

“@ASPNKENIKMATANKU” (@ASPNKENIKMATAN_BOT), 44,757 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/ASPNKENIKMATAN_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.