Bot
Gmail Bot
@GmailBot
On this record: Topic · Growth · Engagement · Citations · Referenced elsewhere · Cite this entry
38,185monthly users
+2,386 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 307373020 |
|---|---|
| Type | Bot |
| Username | @GmailBot |
| First recorded | 13 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/GmailBot |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 85% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 3 Oct 2026, 21:21 | 38,185 | -311 |
| 25 Sept 2026, 02:17 | 38,496 | -1,587 |
| 18 Sept 2026, 21:39 | 40,083 | -318 |
| 16 Sept 2026, 12:55 | 40,401 | +164 |
| 14 Sept 2026, 13:41 | 40,237 | +132 |
| 12 Sept 2026, 23:00 | 40,105 | +1,437 |
| 10 Sept 2026, 21:58 | 38,668 | -1,492 |
| 7 Sept 2026, 20:38 | 40,160 | -160 |
| 4 Sept 2026, 21:19 | 40,320 | +1,160 |
| 3 Sept 2026, 06:24 | 39,160 | -1,223 |
| 1 Sept 2026, 00:16 | 40,383 | -175 |
| 31 Aug 2026, 02:59 | 40,558 | -46 |
| 29 Aug 2026, 03:37 | 40,604 | +250 |
| 27 Aug 2026, 04:25 | 40,354 | +601 |
| 26 Aug 2026, 02:04 | 39,753 | +1,545 |
| 24 Aug 2026, 07:15 | 38,208 | -610 |
| 22 Aug 2026, 16:36 | 38,818 | +507 |
| 21 Aug 2026, 04:13 | 38,311 | +213 |
| 20 Aug 2026, 01:41 | 38,098 | +763 |
| 17 Aug 2026, 20:16 | 37,335 | 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 107 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.
@lyyyy · 27,53014 postsKoleksi Bot
@botkoleksi · 11,75213 posts李老根当狗推日记 @llggs
@llggx · 1,97713 postsETHIO WALET 🇪🇹
@ethio_wallet · 8,3068 postsTelegram İpuçları
@TelegramTipsTR · 227,0518 poststelegram【中文】
@shoushuoqun · 8,3127 postsمدرسه مهارت جاناتان
@janatansc1400 · 11,4855 postsNetClub | نت کلاب
@NetClub_iR · 14,2855 postsAWM商会-广告位招商@BSYYYL
@BSYYYL · 6,6804 postsTeleTop中文索引官方频道
@TeleTopOrg · 34,4464 posts小白实用工具包-达欧集团@Daojt
@Daojiaocheng · 1,0023 postsTelegram免费代理 @FLL8
@fuvip25 · 4,6303 posts辉煌联盟导航
@HHLMDH · 10,3363 postsتقنية | حمادة - 7mada
@its7madatec · 28,6793 postsTelegram新手指引频道
@QingYun00 · 1773 postsTelegram Info
@tginfo · 83,0363 postsTelegram中文导航
@TGXSDH · 4,6873 postsHH-鸿海集团业务【导航】🌇
@cauuuu · 2,2812 posts乐阳|波场地址生成器|trc20靓号|NFT888|能量租用|TRX闪兑 | 模仿地址
@dqtrx · 5,6122 postsHstockORG
@hStockORG · 4,7082 postsBest bots facebook Twitter tiktok google RSS feed أفضل البوتات حماية تحميل ستوري يوتيوب فيسبوك تويتر تيك توك
@ithra_bots · 3652 postsMAMILA TECH
@MAMILA_APP · 3212 postsTrending Apps
@trendingapps · 3,738,8542 posts茶水间导航🧭
@yatai_cheng127 · 5,2972 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.
Referenced elsewhere
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Hacker News
This handle was named 2 times in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Gmail Bot” (@GmailBot), 38,185 monthly users as measured 3 October 2026. Telegram Register, tgregister.com/channel/GmailBot.
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.