Channel
@huilin18688
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
66subscribers
+52 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004312994490 |
|---|---|
| Type | Channel |
| Username | @huilin18688 |
| Created | Between 1 June 2026 and 2 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/huilin18688 |
Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 16:56 | 66 | +1 |
| 28 Oct 2026, 12:05 | 65 | -1 |
| 22 Oct 2026, 10:27 | 66 | -2 |
| 9 Oct 2026, 00:39 | 68 | +2 |
| 28 Sept 2026, 02:22 | 66 | +20 |
| 12 Sept 2026, 09:36 | 46 | +11 |
| 4 Sept 2026, 18:16 | 35 | +21 |
| 3 Sept 2026, 11:22 | 14 | first reading |
12 posts held, back to 2 September 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 3 September 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
🎰 深圳罗湖惠琳半价出击优惠卷 📮 参与条件： 🎫 加入-惠琳 罗湖区 🎫 加入-深圳快乐屋（约课认准轮播和榜单） └ 🎟️ 发言数大于 5 条 🎁 奖品内容： 💰️ p半价优惠卷 × 1 ⚠️ 抽奖说明： 优惠卷有效期为7天、预约可延期 兑奖联系：@huilin186888 （需要提供出击报告 @duobaopuis） 📅 开奖日期：(北京时间) 2026年09月06日 17时05分00秒
https://t.me/posterdesignbysaudagar/2347
老师花名 #慧琳 #已验证 坐标 #罗湖 联系方式 @huilin186888 频道 https://t.me/huilin18688 价格 488起
想做小哥哥手里的奶茶、被你又吸又插💋💋，新人来到，请多多关照
https://t.me/xiuchegbdd （深圳淘宝修车团）已认证上榜，群内设置“定金担保”为所有兄弟出击保驾护航！ 群内每日有白嫖，现金红包，出击补贴等福利抽奖！！！
Channel photo updated
https://telegram.me/+7zn8UG1Uk2oyOGNh 老师群加进去避雷垃圾学生
新人开课，会所出身，身材高挑，会按会骚，喜欢我的小哥哥可以来体验一下哦
#慧琳 已在老友会验证上榜👉 t.me/szxglyhOneBot?startapp=td_838854865 加群机器人: @szxglyhglBot 加群/频道: t.me/szxglyhOneBot?startapp=glist 没有群主只有玩家，纯交流纯分享群 ，分享优质老师，发掘优秀新人。
#慧琳 已在老友会验证上榜👉 t.me/szxglyhOneBot?startapp=td_838854865 加群机器人: @szxglyhglBot 加群/频道: t.me/szxglyhOneBot?startapp=glist 没有群主只有玩家，纯交流纯分享群 ，分享优质老师，发掘优秀新人。
🔥深圳茶楼不定期举行🧧活动，26年千元现金邀请活动已结束，新年红包活动已结束，四五双节千元活动已结束，端午父亲现金🧧活动已结束，后续活动择日进行～～ https://t.me/vip40f 深圳榜 https://t.me/zhenzhenchalou
老师艺名： #惠琳 所在位置: #罗湖 联系方式：@huilin186888 双向机器人：@huilin878bot 价格： #588P 快餐 488 标签： #舌吻 #588P #69 #深喉 #制服 #包时 #熟女 #毒龙 # #快餐
Showing the 12 most recent of 12 posts we hold for @huilin18688. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's 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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“惠琳” (@huilin18688), 66 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/huilin18688.
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.