Bot
TG-Shark | API
@jsp_bot
On this record: Growth · Engagement · Citations · Cite this entry
52,312monthly users
-2,450 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 179996150 |
|---|---|
| Type | Bot |
| Username | @jsp_bot |
| First recorded | 12 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 3 times, most recently 4 September 2026 |
| On Telegram | t.me/jsp_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 1 Sept 2026, 18:44 | 52,312 | +2,781 |
| 31 Aug 2026, 00:47 | 49,531 | -403 |
| 27 Aug 2026, 01:04 | 49,934 | +1,004 |
| 26 Aug 2026, 04:04 | 48,930 | +641 |
| 25 Aug 2026, 00:54 | 48,289 | -1,917 |
| 23 Aug 2026, 09:53 | 50,206 | +737 |
| 19 Aug 2026, 18:56 | 49,469 | -2,246 |
| 17 Aug 2026, 16:48 | 51,715 | -542 |
| 16 Aug 2026, 07:57 | 52,257 | -219 |
| 13 Aug 2026, 10:07 | 52,476 | -41 |
| 12 Aug 2026, 02:43 | 52,517 | no change |
| 11 Aug 2026, 07:41 | 52,517 | -3,900 |
| 9 Aug 2026, 05:02 | 56,417 | +1,655 |
| 7 Aug 2026, 10:50 | 54,762 | 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 33 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 21 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.
@SUCCESSFULBUY · 55,893929 posts𝖳𝖦 𝖲𝗁𝖺𝗋𝗄 𝖯𝗎𝗋𝖼𝗁𝖺𝗌𝗂𝗇𝗀 𝖳𝖾𝖺𝗆
@TgSharkBuy · 60,15392 postsTG-Shark | API •
@TGSharkAPI · 62,49446 posts𝐓𝐆 𝐄𝐀𝐑𝐍𝐈𝐍𝐆 𝐏𝐌 🗣
@TgEarningPm · 24,7837 posts𝐄𝐚𝐫𝐧 𝐖𝐢𝐭𝐡 𝐌𝐀𝐌𝐔𝐍
@Earning_Mamun05 · 12,1824 posts𝐂𝐑𝐘𝐏𝐓𝐎 𝐄𝐀𝐑𝐍𝐈𝐍𝐆 ™
@Crypto_earning_team1 · 13,2492 posts𝗖𝗥𝗬𝗣𝗧𝗢 𝗟𝗘𝗔𝗥𝗡
@Crypto_Learn90 · 15,5142 postsCrypto Profit BD 🇧🇩
@cryptoprofitbd · 5,2482 postsUsername ki lagbe?
@JS_Crypto_Airdrop_6 · 122 postsTG STAR 100%BOT
@refar1000 · 9,5422 postsONLY INSTANT OFFER™
@AdnanBoss3 · 1,9591 postCabyne
@cabyne · 1631 postدلار💵مانی💰پول💸کش🤑
@dollarmoneypolcash · 9561 posteranmonny10
@eranmonny10 · 5,5151 postAPURBA🌱SEED
@hi_num_100 · 3671 postمأموریت = دستمزد
@mamoriat3 · 2641 post༒𝙏𝙀𝙎𝙏 𝘽𝙊𝙏༒
@mehdivip_test · 5421 postPlay-to-Earn P2E
@Play_To_Eran_P2E · 1,2121 postAXO СООБЩЕСТВО ⛔
@PUTINAXOO · 9321 post𝙎𝙤𝙝𝙖𝙣'𝙨 𝘾𝙧𝙚𝙖𝙩𝙞𝙤𝙣
@SohansCreation · 29,8631 post𝐈ꜱᴀɢɪ 𝐄ᴍᴘɪʀᴇ !>🕊️🫶🏻
@spideyyera · 4061 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“TG-Shark | API” (@jsp_bot), 52,312 monthly users as measured 1 September 2026. Telegram Register, tgregister.com/channel/jsp_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.