Bot
抽奖机器人
@Lottery8Bot
On this record: Topic · Growth · Engagement · Citations · Cite this entry
101,535monthly users
-8,946 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | 6420220651 |
|---|---|
| Type | Bot |
| Username | @Lottery8Bot |
| First recorded | 9 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 58 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/Lottery8Bot |
Topic
Giveaways & airdrops — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 76% 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 the other topics.
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 11 Nov 2026, 09:39 | 101,535 | +349 |
| 9 Nov 2026, 13:10 | 101,186 | +179 |
| 8 Nov 2026, 02:31 | 101,007 | +2,057 |
| 7 Nov 2026, 00:17 | 98,950 | -2,794 |
| 5 Nov 2026, 20:45 | 101,744 | -1,933 |
| 4 Nov 2026, 21:11 | 103,677 | -2,058 |
| 2 Nov 2026, 20:49 | 105,735 | -1,124 |
| 1 Nov 2026, 23:06 | 106,859 | -949 |
| 31 Oct 2026, 22:59 | 107,808 | -443 |
| 30 Oct 2026, 23:06 | 108,251 | +769 |
| 29 Oct 2026, 21:56 | 107,482 | -3,446 |
| 29 Oct 2026, 00:17 | 110,928 | -991 |
| 26 Oct 2026, 23:19 | 111,919 | +277 |
| 26 Oct 2026, 00:39 | 111,642 | +226 |
| 25 Oct 2026, 03:15 | 111,416 | +384 |
| 24 Oct 2026, 00:31 | 111,032 | +2,037 |
| 22 Oct 2026, 21:56 | 108,995 | -984 |
| 21 Oct 2026, 22:20 | 109,979 | +877 |
| 20 Oct 2026, 14:48 | 109,102 | +244 |
| 19 Oct 2026, 15:19 | 108,858 | 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.
@ecig6yue · 11815 posts星星𝒇𝒍𝒒社
@fuliqunhanyu0 · 1254 posts南京女仆·星华女仆频道(资料区)
@NJXHLOVE · 1,9273 posts腼腆の小窝
@miantian6doufan · 923 posts反荷包蛋联盟
@ayase525 · 5662 posts暗喻fh
@AYfh666 · 121 post1
@BCNB966 · 2501 postCast New X项目官方频道
@CastNewXnb1314520 · 8441 post坤坤root机
@Fjfjcjxt · 41 post少萝供需【5U/35口令一条】@liu083 (引流中)
@IPhone189promax · 151 post香港外围🌸香港包养🌸香港上门🌸香港学生
@JX_xhy · 1,5051 post墨水鼹通知频道
@MHOVOPD · 731 post倾 听 | Esim 号商频道
@Noe9998 · 381 postSexrain-Media（星雨福利服）
@SexrainMedia · 7281 post折腾App探索｜推荐·频道
@TossTF · 13,9721 post不吃香菜公主的KTV夜场
@buchixiangcaidian2 · 6811 post恶名的小窝
@emingjt · 661 post七月副频道
@fhqiyue6 · 3161 post汇流直播通知频道
@huiliuzhibo · 2,2021 post🎀Emoji 表情 贴纸🎀
@hzqpg · 341 post亚托莉的小窝
@kawaii_atri · 1,7521 post南昌七星瓢虫｜社群公示
@ncqxpcsqgs · 2491 post^呆猪小敏^
@wuwufulii0 · 1051 postElizabeth
@xiaotutxiao · 11 post夜神月の封号小窝
@xihan1111 · 5751 post北京芸熙
@yunxi631 · 2291 post貔｀貅 fh频道
@yywwsh · 141 post天灰的像哭过
@zsk1121 · 1451 post
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 32 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 22 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.
@GCCITY · 157,488244 posts广深出师报告
@fbqun · 62,239194 posts广州资源榜פּוּמְבֵּי『备胎』
@gzact · 33,105112 posts广西南宁资源公开榜
@TG6196 · 19,57144 posts抽奖机器人公告
@TGLottery8 · 99,65235 posts文汐的富哥们
@wwxx168899 · 7467 postsUU的朋友圈
@uumml02 · 9166 posts佛山报告分享
@FSKKB · 14,1805 posts白又白频道
@blfffcc · 6,7534 posts广州柳岩36E(兼职)
@gzthbx666 · 8,0102 posts琳儿公告栏
@panyuliner1 · 1782 posts小航大家庭（跑路狗都去死）🎉🎉
@ty666b · 6,7262 posts小颖ℒℴѵℯ小໊🍒（休假中）
@xiaoying0896 · 5,1422 posts小丸子的频道
@xwz11228 · 642 posts姬小满开课频道
@xxmmf168 · 1,4902 posts宝宝的闺房
@Amionyy · 2191 post小布丁🍮的冰箱
@bdhxjsn123 · 1,1911 post小可爱的频道
@guobaorouya · 4341 post小紫琪
@nituio4 · 3501 post筱桐的幸福小窝😘😘😘
@xiaotong5204ever · 1,1911 post兮兮个人茶艺室
@xixidhhy · 2591 post小雨的频道❤️
@Zoea001 · 1,3401 post
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“抽奖机器人” (@Lottery8Bot), 101,535 monthly users as measured 11 November 2026. Telegram Register, tgregister.com/channel/Lottery8Bot.
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.