
Bot
抽奖机器人
@Lottery8Bot
On this record: Topic · Growth · Engagement · Citations · Cite this entry
107,262monthly users
-3,219 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 | 18 October 2026 |
| Measurements held | 38 |
| Confirmed unchanged | 1 time, most recently 18 October 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 18 Oct 2026, 16:14 | 107,262 | +275 |
| 17 Oct 2026, 13:09 | 106,987 | +423 |
| 15 Oct 2026, 18:31 | 106,564 | +1,408 |
| 14 Oct 2026, 17:09 | 105,156 | +4,540 |
| 13 Oct 2026, 06:36 | 100,616 | -5,755 |
| 9 Oct 2026, 02:18 | 106,371 | +1,988 |
| 4 Oct 2026, 15:40 | 104,383 | +5,538 |
| 26 Sept 2026, 15:58 | 98,845 | -2,925 |
| 19 Sept 2026, 16:39 | 101,770 | -2,012 |
| 17 Sept 2026, 01:20 | 103,782 | +646 |
| 15 Sept 2026, 03:20 | 103,136 | -682 |
| 13 Sept 2026, 10:18 | 103,818 | -2,523 |
| 11 Sept 2026, 13:36 | 106,341 | +201 |
| 9 Sept 2026, 00:56 | 106,140 | -790 |
| 5 Sept 2026, 15:41 | 106,930 | -517 |
| 3 Sept 2026, 14:16 | 107,447 | -256 |
| 2 Sept 2026, 07:05 | 107,703 | -193 |
| 1 Sept 2026, 09:14 | 107,896 | -180 |
| 30 Aug 2026, 04:13 | 108,076 | -3,029 |
| 29 Aug 2026, 00:56 | 111,105 | 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 · 11115 posts星星𝒇𝒍𝒒社
@fuliqunhanyu0 · 1274 posts南京女仆·星华女仆频道(资料区)
@NJXHLOVE · 1,9433 posts腼腆の小窝
@miantian6doufan · 983 posts反荷包蛋联盟
@ayase525 · 6272 posts暗喻fh
@AYfh666 · 131 post1
@BCNB966 · 2591 postCast New X户籍猎手官方频道
@CastNewXnb1314520 · 7151 post坤坤root机
@Fjfjcjxt · 41 post少萝供需【5U/35口令一条】@liu083 (引流中)
@IPhone189promax · 151 post墨水鼹通知频道
@MHOVOPD · 741 post倾 听 | Esim 号商频道
@Noe9998 · 381 postSexrain-Media(星雨福利服)
@SexrainMedia · 7241 post不吃香菜公主的KTV夜场
@buchixiangcaidian2 · 6921 post恶名的小窝
@emingjt · 681 post七月副频道
@fhqiyue6 · 3781 post汇流直播通知频道
@huiliuzhibo · 1,9651 post🎀Emoji 表情 贴纸🎀
@hzqpg · 41 post亚托莉的小窝
@kawaii_atri · 1,4991 post^呆猪小敏^
@wuwufulii0 · 971 post夜神月の封号小窝
@xihan1111 · 5291 post全国莞式全套会所
@yubaoyybb · 21 post北京芸熙
@yunxi631 · 2341 post貔`貅 fh频道
@yywwsh · 151 post天灰的像哭过
@zsk1121 · 1491 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 24 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 23 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 · 155,058166 posts广州资源榜פּוּמְבֵּי『备胎』
@gzact · 31,79051 posts抽奖机器人公告
@TGLottery8 · 53,51835 posts广西南宁资源公开榜
@TG6196 · 19,13021 posts海盗免费社工机器人【官方频道】
@HaiDaoSgk · 50,4253 posts琳儿公告栏
@panyuliner1 · 1732 posts小航大家庭(跑路狗都去死)🎉🎉
@ty666b · 6,9132 posts小颖ℒℴѵℯ小໊🍒(休假中)
@xiaoying0896 · 5,3092 posts宝宝的闺房
@Amionyy · 1861 post白云东平可可🦋小鱼塘
@baiyunkekeyo · 2,6611 post微微小花园
@baiyunxiao · 2281 post小布丁🍮的冰箱
@bdhxjsn123 · 1,2371 postDoriya Network
@DoriyaNet · 2,4611 post小可爱的频道
@guobaorouya · 9581 post姜夏的频道
@jxjxjxq · 7961 post天河区(服务型) 乐伊/可舌👅可69-开课中
@lishadehougond · 2,7181 post奶糖🍬性趣研究中心
@thnait · 1921 post全国莞式全套会所
@tiancaijiang520 · 11 post筱桐的幸福小窝😘😘😘
@xiaotong5204ever · 1,6871 post兮兮个人茶艺室(休息🀄️)
@xixidhhy · 1811 post星空空の自留地
@xkkzld · 1051 post小星星的个人频道
@yuanqq168 · 6041 post小雨的频道❤️
@Zoea001 · 1,0671 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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“抽奖机器人” (@Lottery8Bot), 107,262 monthly users as measured 18 October 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.