Telegram RegisterThe public register of Telegram

Bot

Aploder

@Aploooode147bot

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

30,631monthly users

-9,539 since we began measuring on 21 August 2026

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

Register entry

Telegram ID8454954314
TypeBot
Username@Aploooode147bot
First recorded21 August 2026
Last confirmed live5 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/Aploooode147bot

Growth

30,63140,17035,400.521 August 2026 — 40,170 monthly users21 August 2026 — 40,170 monthly users25 August 2026 — 39,041 monthly users29 August 2026 — 35,184 monthly users1 September 2026 — 32,893 monthly users3 September 2026 — 31,639 monthly users5 September 2026 — 30,631 monthly users21 August 20265 September 2026
7 measurements spanning 15 days, net -9,539. 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 29,200–41,601 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
5 Sept 2026, 09:5630,631-1,008
3 Sept 2026, 10:2731,639-1,254
1 Sept 2026, 06:4632,893-2,291
29 Aug 2026, 04:5535,184-3,857
25 Aug 2026, 05:1839,041-1,129
21 Aug 2026, 17:0040,170no change
21 Aug 2026, 15:1540,170first 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.

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

“Aploder” (@Aploooode147bot), 30,631 monthly users as measured 5 September 2026. Telegram Register, tgregister.com/channel/Aploooode147bot.

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.