Telegram RegisterThe public register of Telegram
Telegram profile photo for Auto Join Request Approver Bot

Bot

Auto Join Request Approver Bot

@Auto_Approver_bot

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

24,054monthly users

+1,523 since we began measuring on 6 August 2026

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

Register entry

Telegram ID8772383682
TypeBot
Username@Auto_Approver_bot
First recorded15 August 2026
Last confirmed live25 August 2026
Measurements held8
Confirmed unchanged2 times, most recently 25 August 2026
On Telegramt.me/Auto_Approver_bot

Growth

22,53124,24723,3896 August 2026 — 22,531 monthly users8 August 2026 — 24,247 monthly users11 August 2026 — 23,308 monthly users14 August 2026 — 23,945 monthly users15 August 2026 — 23,945 monthly users17 August 2026 — 23,084 monthly users20 August 2026 — 23,826 monthly users24 August 2026 — 24,054 monthly users24,0546 August 202624 August 2026
8 measurements spanning 18 days, net +1,523. 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 22,274–24,504 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
24 Aug 2026, 21:0724,054+228
20 Aug 2026, 18:1723,826+742
17 Aug 2026, 16:4623,084-861
15 Aug 2026, 17:1723,945no change
14 Aug 2026, 21:3423,945+637
11 Aug 2026, 10:1323,308-939
8 Aug 2026, 13:1824,247+1,716
6 Aug 2026, 14:4722,531first 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 1 registered channel — 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.

“Auto Join Request Approver Bot” (@Auto_Approver_bot), 24,054 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/Auto_Approver_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.