Bot
pgon
@pgon
On this record: Growth · Engagement · Citations · Cite this entry
30,656monthly users
-554 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 7732608454 |
|---|---|
| Type | Bot |
| Usernames | @pgon @PGON_robot |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/pgon |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 14 Aug 2026, 21:18 | 30,656 | no change |
| 14 Aug 2026, 16:47 | 30,656 | -578 |
| 13 Aug 2026, 21:25 | 31,234 | no change |
| 13 Aug 2026, 15:37 | 31,234 | -653 |
| 12 Aug 2026, 12:53 | 31,887 | -104 |
| 10 Aug 2026, 13:34 | 31,991 | +579 |
| 7 Aug 2026, 18:31 | 31,412 | +202 |
| 5 Aug 2026, 22:18 | 31,210 | 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 28 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.
@PGON_wallet · 38,80461 postsWorld Crypto Project...💻📲
@WorldGameProject · 2,7204 postsEdoo: курсы для IT и диджитал-специалистов
@edoocate · 9,4933 postsVegas Grand
@vegasplay · 1,4543 postsИнфошум
@CryproZone1 · 2942 postsDeCenter — блокчейн, биткоин, инвестиции
@DeCenter · 1,959,1782 postsРом
@dhsggsnss · 1992 postsХалява от Лечи
@promootlechi · 1822 postsavtodociRF
@avtodociRF · 61 postКРИПТО БАНКИР💰 | Инвестиции в криптовалюту
@bankirya · 5,4771 postкрипта/блокчейн
@crypto_blockchain_inform · 271 postCʀʏᴘᴛᴏ X ʟx
@cryptoxlx · 771 postКрипта с Алексеем
@freeCrypt2024 · 691 postTON игры и проги 🕹
@GamesCryptoTG · 261 postХалява от хайзенберга
@hizenbr · 461 postGiftcoin
@jettcoin · 951 post𝙇𝙞𝙛𝙚 𝙇𝙞𝙣𝙚 𝘼𝙡𝙡 𝙀𝙖𝙧𝙣𝙞𝙣𝙜 𝟯𝟲
@Life_Line_All_Earning36 · 1,0471 postMickey on TON
@mickeygypsyonton · 1,6561 postNote me, TON
@notemeton · 1,3891 postStrannik
@odinokiii_strannik · 651 postОтзывы и кейсы Валихан
@reviewsValihan · 31 postLIVE — Telegram, AI и технологии
@tlive · 1,873,4011 postUnilive
@uniliverus · 261 postX Top Casino 2026 год| Бонусы
@xtopcasino · 1,4701 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“pgon” (@pgon), 30,656 monthly users as measured 14 August 2026. Telegram Register, tgregister.com/channel/pgon.
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.