Bot
лавэшка — криптокошелёк
@laveshka
On this record: Growth · Engagement · Citations · Cite this entry
48,260monthly users
+33,547 since we began measuring on 5 September 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 8861684133 |
|---|---|
| Type | Bot |
| Username | @laveshka |
| First recorded | 5 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/laveshka |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 19 Sept 2026, 02:58 | 48,260 | +2,031 |
| 14 Sept 2026, 17:40 | 46,229 | +2,846 |
| 13 Sept 2026, 07:17 | 43,383 | +4,756 |
| 11 Sept 2026, 08:59 | 38,627 | +7,789 |
| 8 Sept 2026, 14:56 | 30,838 | +16,125 |
| 5 Sept 2026, 19:20 | 14,713 | no change |
| 5 Sept 2026, 17:17 | 14,713 | 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 48 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.
@binnione · 67,1437 posts𝗘𝗔𝗥𝗡𝗜𝗡𝗘 𝗪𝗜𝗧𝗛 𝗖𝗥𝗬𝗣𝗧𝗢
@earninge_with_crypto · 34,1987 postsбензин
@benzin · 68,9515 posts𝗝𝗶𝗵𝗮𝗱 𝗖𝗿𝘆𝗽𝘁𝗼 𝗢𝗳𝗳𝗶𝗰𝗶𝗮𝗹シ︎
@Jihad_Crypto_Official_BD · 42,5145 postsLegenda_VV_Dele
@LegendaVDele · 23,0674 postsNFTGalaxy
@nftTELEGRAMN · 37,2024 postsCrypto Чайка
@crypto_chaika · 47,0643 postsInsider TON
@InsiderT0N · 98,6043 posts𝗔𝗕 𝗥𝗮𝘂𝐅 𝗧𝗶𝗽𝘀
@abrauftips · 36,1602 posts𝐀𝐢𝐫𝐝𝐫𝐨𝐩 𝐨𝐟𝐟𝐢𝐜𝐢𝐚𝐥 𝟒𝟐𝟎
@Airdropofficial420 · 95,4832 postsAlex TON
@Alex_TON17 · 63,0412 postsBD INCOME TIPS
@bd_income_tips_6t9 · 78,6502 posts♨️ Переходник ♨️
@CoLTnftcha · 522 postsCPP EARNING Official ☠️
@cpp_earning · 120,1152 postsДиректор Подарков
@dayroxton · 42,6172 posts𝐅𝐑𝐄𝐄 𝐄𝐀𝐑𝐍𝐈𝐍𝐆 𝐓𝐆 🍥
@FREE_EARNING_TG · 32,0462 postsFree Telegram premium
@Free_Premium_and_star · 1542 posts@laveshka — криптокошелек
@laveshka_news · 4,9712 postsNew Airdrop Bangla | AiBangla
@newairdropbangla · 34,7052 postsNFT 13
@nft13onton · 62,8332 postslowake
@noazartchannel · 186,6702 poststitrik
@titrikz · 29,5052 postsПЕПЕНСКИЙ
@pepenskyy · 36,6011 postTORGASH NFT
@torgash_nft · 32,7051 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“лавэшка — криптокошелёк” (@laveshka), 48,260 monthly users as measured 19 September 2026. Telegram Register, tgregister.com/channel/laveshka.
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.