Bot
BeeGifts
@BeeGft_bot
On this record: Growth · Engagement · Citations · Cite this entry
19,530monthly users
+1,956 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8646139581 |
|---|---|
| Type | Bot |
| Username | @BeeGft_bot |
| First recorded | 16 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/BeeGft_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 17 Aug 2026, 19:46 | 19,530 | +80 |
| 16 Aug 2026, 20:10 | 19,450 | no change |
| 15 Aug 2026, 01:08 | 19,450 | +387 |
| 13 Aug 2026, 14:17 | 19,063 | -118 |
| 11 Aug 2026, 12:35 | 19,181 | +242 |
| 10 Aug 2026, 12:52 | 18,939 | +812 |
| 7 Aug 2026, 08:30 | 18,127 | +553 |
| 6 Aug 2026, 01:31 | 17,574 | 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 65 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.
@TON_Elixir · 218,724124 postsCRYPTO METEORA ☄️
@Crypto_Meteora · 332,132118 postsCRYPTO ZARYAD⚡️
@CryptoZaryad · 328,26591 postsAkira v TONe
@akiravton · 13,93488 postsCrypto Чайка
@crypto_chaika · 45,64487 postsLipTON | Инвестиции
@LipTON_v_dele · 14,40083 postsGlusheMoney
@glushemoney · 133,22780 postsCrypto_Tiger 🐅
@The_Crypto_Tiger · 65,58548 postsАКРОНИМ
@AcronummT · 46,23538 postsCRYPTOMANIA
@cryptomania2026 · 120,89234 postsBeeGifts News
@BeeGiftsNews · 21,16631 postsNFT от frina
@NFT_frina · 15,17226 posts💎Крипто Гем💎
@crypto_gem35 · 4,20622 postsGift Caps | Розыгрыш Подарков
@giftcaps11 · 15,65322 postsFree gift NFT
@Freeg1ftNfT · 12,13320 posts𝐓𝐨𝐫𝐟𝐢𝐧 | 𝐍𝐅𝐓
@Torfin_NFT · 14,40220 postsCrypto&Brunette
@cryptobrunette · 83,80115 posts「 𝗞𝗡𝗧x̲𝗠𝗥𝗞𝗧 」
@KNT007B · 15,22213 postsGift News
@GiftNews_Tg · 10,84811 postsGiftVerse - NFT подарки
@Gift_Verse_Nft · 15,68910 postsALIEN/CRYPTO
@aliencryptoua · 7,7659 postsBEAST
@beast_nfts · 11,6297 postsHot Firedrop
@hot_firedrop_drop · 7,3067 postsСообщество maynTon
@maynTon · 1,3527 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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“BeeGifts” (@BeeGft_bot), 19,530 monthly users as measured 17 August 2026. Telegram Register, tgregister.com/channel/BeeGft_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.