
Bot
Wen Lambo?!
@wen_Lambo_bot
On this record: Growth · Engagement · Citations · Cite this entry
52,364monthly users
+41,684 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 | 7877265379 |
|---|---|
| Type | Bot |
| Username | @wen_Lambo_bot |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| On Telegram | t.me/wen_Lambo_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 12 Aug 2026, 15:22 | 52,364 | no change |
| 12 Aug 2026, 06:52 | 52,364 | +10,609 |
| 10 Aug 2026, 05:50 | 41,755 | +10,307 |
| 9 Aug 2026, 06:43 | 31,448 | -239 |
| 8 Aug 2026, 06:04 | 31,687 | +3,077 |
| 7 Aug 2026, 04:32 | 28,610 | +17,930 |
| 6 Aug 2026, 00:52 | 10,680 | 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 97 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.
@eduardinvest · 1,473,827315 postsLambo Speaking RU
@lambospeak_RU · 10,56668 postsWen Lambo? Now!
@lambospeak · 63,58765 posts🦄 Max.ton
@gramlow · 24,20949 postsCrypto Oborona En
@crypto_oborona_en · 63,77716 postsTyler Durden @MRKT
@tontap1 · 2,62013 postsCrypto Medwed
@cryptomedwed · 150,13611 postsCrypto Medwed En
@crypto_medwed · 39,3169 postsCrypto Oborona
@crypto_oborona · 135,2159 postsCrypto Lambo GRAM
@Crypto_LamboTON · 9918 postsПодполье Пабло
@phenomen_ton · 1,1758 postsADrops | Crypto & Gifts
@adropscoin · 325,4137 postsCrypto Cyber Future #MTONGA
@cryptofuturecyber · 697 posts<\> Sharding, TON's, two Jetons </>.
@ton2keng · 635,2947 posts25/8⭕️
@morozovi_1 · 5,5586 postsCryptoShansEdge
@CryptoShansEdge · 1,0415 postsХомячий памп
@hamsterspump · 22,7415 postsThermos News
@thermos_news · 96,0685 posts💸💰 Income LATAM 💰💸
@IncomeLatam · 27,5754 postsPABLO
@pablo_ngb · 2564 postsМысли Семенчука
@semenchuk · 1,318,7154 posts<\> Шардинг, TON'ы, два Жетона </>.
@ton2k · 251,4894 postsWeWantTon💎
@wewant_ton · 3304 postsБЕЗ "FOMO" и Убытков в крипте 🫡
@neverfakecoins · 8863 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Wen Lambo?!” (@wen_Lambo_bot), 52,364 monthly users as measured 12 August 2026. Telegram Register, tgregister.com/channel/wen_Lambo_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.