Bot
Thermos
@thermos
On this record: Growth · Engagement · Citations · Cite this entry
23,398monthly users
-6,465 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 | 7548680684 |
|---|---|
| Type | Bot |
| Usernames | @thermos @thermos_giftbot |
| First recorded | 15 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 17 August 2026 |
| On Telegram | t.me/thermos |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 17 Aug 2026, 09:52 | 23,398 | no change |
| 16 Aug 2026, 15:25 | 23,398 | +112 |
| 15 Aug 2026, 19:15 | 23,286 | no change |
| 13 Aug 2026, 12:17 | 23,286 | -6,036 |
| 10 Aug 2026, 11:46 | 29,322 | -441 |
| 7 Aug 2026, 10:12 | 29,763 | -100 |
| 6 Aug 2026, 00:42 | 29,863 | 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 176 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.
@semenchuk · 1,308,007118 postsThermos News
@thermos_news · 95,642109 postsIQlton Airdrops & Gifts
@IQlton · 7,16332 postsNft 2.0 Crypto 😍
@not_2_0 · 11,60929 postsBAFY (Best Airdrops For You)
@Gleam_AquaProtocol_Bot · 32,90524 postsTelegram Gifts Parser
@TgGiftParser · 10120 posts𝗣𝗘𝗣𝗘 𝗪𝗧𝗙 𝗚𝗜𝗙𝗧 🐸
@PEPEWTFGIFT · 3,87216 postsrevert
@revert_tg · 3516 postsBossFlor&DarDanellu
@BossFlor_DarDanellu · 10915 posts@REDBIT_NEWS
@REDBIT_NEWS · 49015 postsNews Telegram|NFT|Новости Тон
@TG_NFT_N3WS · 3815 postsNFT простір [Подарунки] 🇺🇦
@nft_space_gifts · 2,17814 postsGIF NFT
@crypto_nft_gif · 1,55113 postsG1ft Hunter
@g1ft_hunter · 15613 postsДайте TON!
@givemetonru · 2,245,09913 posts𝙉𝙁𝙏 | Сенсации 💎
@NFTSensation · 87013 postsКРИПТО САМУРАЙ 🥷🐲
@CryptoSamurai_1 · 5,61112 postsДневник КликерМанки NFT
@clicermania · 3,81710 postsGIFT CARGO
@giftcargo · 4310 postsСтикеролог Владимир
@stickerolog · 5710 postsSamoX & Slycat Hub 🐳
@Samoxhub · 3,4669 postsCrypto Boss
@thisCryptoBoss · 2359 postsMeta M5
@m5_ton · 93,3058 postsMerge Exodus 🕊
@mergexodus · 17,6948 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.
“Thermos” (@thermos), 23,398 monthly users as measured 17 August 2026. Telegram Register, tgregister.com/channel/thermos.
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.