Telegram RegisterThe public register of Telegram

Bot

aploder1

@aplodeere1_bot

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

17,094monthly users

+3,341 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 ID7992932498
TypeBot
Username@aplodeere1_bot
First recorded18 August 2026
Last confirmed live25 August 2026
Measurements held9
Confirmed unchanged2 times, most recently 25 August 2026
On Telegramt.me/aplodeere1_bot

Growth

13,75317,09415,423.57 August 2026 — 13,753 monthly users10 August 2026 — 14,419 monthly users12 August 2026 — 15,512 monthly users14 August 2026 — 15,672 monthly users17 August 2026 — 15,936 monthly users18 August 2026 — 15,936 monthly users18 August 2026 — 16,450 monthly users23 August 2026 — 16,905 monthly users24 August 2026 — 17,094 monthly users7 August 202624 August 2026
9 measurements spanning 17 days, net +3,341. 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,252–17,595 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
24 Aug 2026, 16:2717,094+189
23 Aug 2026, 02:2416,905+455
18 Aug 2026, 15:5816,450+514
18 Aug 2026, 10:2515,936no change
17 Aug 2026, 16:2815,936+264
14 Aug 2026, 16:1515,672+160
12 Aug 2026, 08:0815,512+1,093
10 Aug 2026, 09:2414,419+666
7 Aug 2026, 18:0313,753first 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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“aploder1” (@aplodeere1_bot), 17,094 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/aplodeere1_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.