Bot
@appss - Explore x Play x Earn
@appss
On this record: Growth · Engagement · Citations · Cite this entry
51,786monthly users
-66,843 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 7643175386 |
|---|---|
| Type | Bot |
| Usernames | @appss @appsshubbot |
| First recorded | 10 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 12 August 2026 |
| On Telegram | t.me/appss |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 11 Aug 2026, 21:41 | 51,786 | no change |
| 11 Aug 2026, 20:53 | 51,786 | -40,684 |
| 10 Aug 2026, 17:06 | 92,470 | no change |
| 7 Aug 2026, 20:01 | 92,470 | -8,674 |
| 6 Aug 2026, 18:00 | 101,144 | -17,485 |
| 6 Aug 2026, 00:49 | 118,629 | first 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 35 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.
@appss_channel · 8,96934 posts@appss | Боты и мини-приложения Telegram
@appss_channel_ru · 51516 postsTON Insights
@ton_insights · 9,3788 postsЗаписки о TON блокчейне
@ton_insights_ru · 6,3795 postsnest
@nest_dex · 120,7544 postsOOIA - TON NFT Marketplace
@ooiaton · 278,1084 postsStepHero News
@stepheronews · 373,3284 postsOOIA - TON NFT Marketplace RU
@ooiaton_ru · 5,8073 postsفروش رفرال
@ReferralCR · 7,0983 postsStreet Fury by OYABUN Announcement
@street_fury · 52,6203 postsMOON 🚀
@ton1moon · 346,1153 postsTelegram bot earn
@bot_earn_telegram · 1462 postsBotNews
@BotNewsBR · 7,0252 postsLotcoin Announcement
@lotcoin_channel · 5,0372 postsMark Okhman | @appss
@markappss · 3092 postsMOON App
@moon1app · 36,3442 postsAxiom Game Labs EN
@AGL_games · 5811 postiTeleStore
@itelestore · 3,1681 postPlaymuse RU
@playmuseru · 1,2281 postRaccoonCoin (RACC)
@racccoin · 861 postStorm Trade | News ⚡️
@storm_trade_news · 961,4901 postClickHub Updates
@theclickhub · 2,2771 postTonstakers
@thetonstakers · 948,9661 postTon Raffles En Channel
@tonraffles_en · 1,338,9251 post
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“@appss - Explore x Play x Earn” (@appss), 51,786 monthly users as measured 11 August 2026. Telegram Register, tgregister.com/channel/appss.
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.