Bot
EARNIKA
@Earnikabot
On this record: Growth · Engagement · Citations · Cite this entry
71,231monthly users
-11,728 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 | 8757914328 |
|---|---|
| Type | Bot |
| Username | @Earnikabot |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Earnikabot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 14 Aug 2026, 01:55 | 71,231 | -1,784 |
| 12 Aug 2026, 16:35 | 73,015 | -4,440 |
| 11 Aug 2026, 15:47 | 77,455 | -1,910 |
| 11 Aug 2026, 02:22 | 79,365 | no change |
| 10 Aug 2026, 14:04 | 79,365 | -1,197 |
| 9 Aug 2026, 12:41 | 80,562 | -1,029 |
| 8 Aug 2026, 10:10 | 81,591 | -1,368 |
| 7 Aug 2026, 00:47 | 82,959 | 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 79 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.
@trustedappss · 57720 postsINCOME SIR
@INCOME_SIR · 1,15218 postsEARNING APP STORE
@Real_Earnings_Apps · 1,10218 postsDopamin Detox
@Taka_Income_BD_Official · 1,27918 postsONLINE FREE INCOME 🤑
@Free_Online_Income937 · 97,85514 postsSkill & Earn BD
@SkillEarnBDTeam · 1,16710 postsTTTTTT
@amdadad · 213 posts𝗕𝗱 𝗪𝗲𝗯 𝗛𝘂𝗯🤑
@bdwebhub · 77,8883 posts𝗘𝗮𝗿𝗻𝐗 𝗢𝗳𝗳𝗶𝗰𝗶𝗮𝗹 𝗕𝗗
@EarnX_BD · 5,7623 postsIncome HZ
@IncomeHZ18 · 9,3313 posts𝗜𝗻𝗰𝗼𝗺𝗲 𝗧𝗶𝗽𝘀 𝗕𝗗𝟭𝟭
@incometipsbd11 · 18,0503 posts𝗩𝗜𝗣 𝗜𝗡𝗦𝗧𝗔𝗡𝗧 𝗞𝗨𝗣⚕️
@Vip_Instant_Kupp · 26,0823 postsFree Earnings
@Aird555 · 119,8072 postsOnline income
@AMMM4444 · 45,4542 postsBD INCOME ALL SAID🔥
@bdincomeallsaid200 · 202 postsEarnings
@earnings365 · 52,4232 postsمكاسب مجانية
@faga71 · 11,1222 postsFree Earning BD
@freeearningebd · 692 posts𝗙𝗿𝗲𝗲 𝗜𝗻𝗰𝗼𝗺𝗲 𝗕𝗗 𝟮.𝟬
@FreeIncomeBDextra · 5152 postsরেফার টু রেফার💸
@income24f · 382 postsFREE EARNING
@spremum · 1342 postsTeam Crypto Hunters 💰
@teamcryptohunters · 1152 posts𝐓𝐡𝐞 𝐑𝐨𝐧𝐲
@therony · 7,0672 postsUpdate Airdrop Hunter 🤝💸🪙
@UpdateAirdropHunterkup · 7,3112 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“EARNIKA” (@Earnikabot), 71,231 monthly users as measured 14 August 2026. Telegram Register, tgregister.com/channel/Earnikabot.
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.