Bot
Gifts Battle
@GiftsBattle_bot
On this record: Growth · Engagement · Citations · Cite this entry
91,628monthly users
+15,067 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 | 7918810157 |
|---|---|
| Type | Bot |
| Username | @GiftsBattle_bot |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/GiftsBattle_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 13 Aug 2026, 12:45 | 91,628 | +1,236 |
| 12 Aug 2026, 14:37 | 90,392 | +5,361 |
| 10 Aug 2026, 19:53 | 85,031 | no change |
| 10 Aug 2026, 11:28 | 85,031 | -56 |
| 9 Aug 2026, 11:33 | 85,087 | +5,247 |
| 8 Aug 2026, 08:38 | 79,840 | +1,729 |
| 7 Aug 2026, 08:27 | 78,111 | +1,550 |
| 6 Aug 2026, 02:50 | 76,561 | 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 201 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.
@giftsbattle · 349,28071 posts𝐍𝐅𝐓 | 𝐒𝐡𝐚𝐱
@shaxnft23 · 1,09219 postsMint Na Nule
@mintnanule · 2117 postsTweedlex gifts @mrkt
@TWEDgifts · 17515 postsGB ПРОМОКОДЫ
@GBpromo1 · 24012 posts🎁 CVV investment 🍓
@cvvmbw · 5308 postsNFT news channel🎰
@NFTFreeChannel · 56 postsSPARTANS
@Spartans_Com · 43,7495 postsBig win
@BIG_WINQ · 63,6574 postsКрипто Штурман
@cryptoshurman · 9,5704 postsGIFTS BATTLE PROMO
@GIFTSPROMIKI · 154 posts1win️
@BIG_1WlN · 48,6403 postsCasino BONUS
@crypto_pulse_news · 64,0193 postsДэндиДэп
@depay_bratishka · 183 posts🏔️❄️~челен бобра~🏔️❄️
@Five_Freddy_666 · 253 postsGifts Battle | StonksGift Промокоды
@giftsbattle_promocods · 10,4163 postsGiftsShtorm
@giftsshtorm · 1,1463 postsОбезьяна в gift
@monkey_v_gifts · 1,2013 postsЗаписная книжка
@username_in_telegramm · 143 postsgg🏳
@ggett_ruone · 942 postsGIFTS PRESIDENT | TELEGRAM
@giftspresident · 5462 postsRoblox OOF
@robloxOOF · 42 postsᏦᎪᏞᏴᏆᎷ ❤️🩹
@statuslarim_tme · 42 postsТимур и его TONанда 👽
@tonanda · 1362 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Gifts Battle” (@GiftsBattle_bot), 91,628 monthly users as measured 13 August 2026. Telegram Register, tgregister.com/channel/GiftsBattle_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.