Bot
Predict with Polymarket
@ipredict
On this record: Growth · Engagement · Citations · Cite this entry
39,682monthly users
-22,792 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 | 8424715612 |
|---|---|
| Type | Bot |
| Username | @ipredict |
| First recorded | 12 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 22 August 2026 |
| On Telegram | t.me/ipredict |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 20 Aug 2026, 20:34 | 39,682 | -3,250 |
| 17 Aug 2026, 21:37 | 42,932 | -4,362 |
| 15 Aug 2026, 09:12 | 47,294 | -6,379 |
| 12 Aug 2026, 02:26 | 53,673 | no change |
| 11 Aug 2026, 17:44 | 53,673 | -4,073 |
| 7 Aug 2026, 19:51 | 57,746 | -4,728 |
| 6 Aug 2026, 00:42 | 62,474 | 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 106 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.
@bitochekvko · 42,207219 postsPredict with Polymarket
@predictapp_en · 5,35853 postsPredict with Polymarket RU
@predictapp_ru · 1,57221 postsDropsnap
@dropsnap · 7,10310 postsЛУДОпреключения с Кешей
@ludikkeshaaa · 4509 postsTTC | TimeToCrypto
@nftTTC · 35,4098 postsGetgems NFT RU
@getgemsrus · 110,3537 postsSatoshi ₿ ꘜ TON
@SatoshiNakamoTON · 53,5897 postsАирдропы (AirDrop), бонусы, раздачи, криптовалюта
@everyday_airdrops · 2,9416 postsShardChain
@ShardChain · 22,5256 postsSTON.fi فارسی
@stonfi_fa · 14,5386 postsInsight TON • News Web3 Trends
@web3newston · 12,7966 postsCRYPTEP
@cryptep · 64,3675 postsDAO1
@DAO1_app · 17,1175 postsGetgems NFT
@getgems · 276,6505 postsKnyazev Stars | Telegram & Gifts News
@KnyazevStars · 725 postsPresale RU
@presaleru · 41,4235 postsSCUF COIN | TON
@scufcointon · 7,9595 postsTON CABAL🦞
@Ton_cabal · 13,9485 postsتون لاورز | TonLovers
@TonLovers · 57,1965 postsThe Open Platform
@topco · 29,3975 postsInvestment kingyru 💎 EN
@investkingyru_en · 20,2414 postsТапаномика 💷
@katanatapaet · 21,6204 postsNotcoin Russia
@notcoin_russia_ruchanal · 23,1774 posts
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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“Predict with Polymarket” (@ipredict), 39,682 monthly users as measured 20 August 2026. Telegram Register, tgregister.com/channel/ipredict.
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.