Telegram RegisterThe public register of Telegram
Telegram profile photo for Telegram Apps Center

Bot

Telegram Apps Center

@tapps_bot

Verified by Telegram2 usernames

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

55,977monthly users

+429 since we began measuring on 5 August 2026

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

Register entry

Telegram ID6669225483
TypeBot
Usernames@tapps @tapps_bot
First recorded11 August 2026
Last confirmed live21 August 2026
Measurements held12
Confirmed unchanged5 times, most recently 21 August 2026
On Telegramt.me/tapps_bot

Growth

55,53257,25056,3915 August 2026 — 55,548 monthly users7 August 2026 — 55,532 monthly users7 August 2026 — 55,532 monthly users10 August 2026 — 57,150 monthly users11 August 2026 — 57,150 monthly users11 August 2026 — 57,150 monthly users14 August 2026 — 57,250 monthly users14 August 2026 — 57,250 monthly users17 August 2026 — 55,963 monthly users17 August 2026 — 55,963 monthly users19 August 2026 — 55,977 monthly users19 August 2026 — 55,977 monthly users55,9775 August 202619 August 2026
12 measurements spanning 14 days, net +429. 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 55,274–57,508 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
19 Aug 2026, 20:1355,977no change
19 Aug 2026, 15:2655,977+14
17 Aug 2026, 23:4555,963no change
17 Aug 2026, 09:5355,963-1,287
14 Aug 2026, 04:5957,250no change
14 Aug 2026, 03:2657,250+100
11 Aug 2026, 20:0057,150no change
11 Aug 2026, 01:0257,150no change
10 Aug 2026, 23:5557,150+1,618
7 Aug 2026, 21:1155,532no change
7 Aug 2026, 17:1455,532-16
5 Aug 2026, 22:0255,548first 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 584 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Telegram Apps Center” (@tapps_bot), 55,977 monthly users as measured 19 August 2026. Telegram Register, tgregister.com/channel/tapps_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.