Channel
@lilvhy
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
826subscribers
+738 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003974228196 |
|---|---|
| Type | Channel |
| Username | @lilvhy |
| Created | 21 August 2026 — measured — dated from the channel’s first post |
| First recorded | 24 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/lilvhy |
Hacking & security — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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 |
|---|---|---|
| 13 Nov 2026, 10:10 | 826 | +24 |
| 5 Nov 2026, 12:40 | 802 | -2 |
| 29 Oct 2026, 04:16 | 804 | -2 |
| 22 Oct 2026, 19:47 | 806 | +6 |
| 16 Oct 2026, 10:16 | 800 | +6 |
| 9 Oct 2026, 22:58 | 794 | +26 |
| 30 Sept 2026, 18:02 | 768 | +145 |
| 16 Sept 2026, 20:56 | 623 | +130 |
| 9 Sept 2026, 09:37 | 493 | +39 |
| 31 Aug 2026, 18:03 | 454 | +338 |
| 25 Aug 2026, 04:13 | 116 | +28 |
| 24 Aug 2026, 16:45 | 88 | first reading |
2 posts held, back to 21 August 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 2 posts for this entry, the most recent from 23 August 2026. An engagement rate over an empty window would be a number about nothing.
👉👉李律核验机器人👈👈｜快速核验 · 多接口聚合 🤖 核验不必东奔西走 🤖 李律核验机器人集齐所有核验功能！ 免费支持法人验证，人脸验证，运营商验证，银行卡验证，12306验证，实名验证等 需要核验信息的时候，不用再到处找接口。 💐 功能免费，无需签到 🐻 推广可活动额度 额度每日自动刷新无需签到 李律核验机器人整合多种常用核验功能，一台机器人即可完成操作，查询流程简单、响应快速。 支持多种核验场景，包括实名要素、银行卡要素、企业信息、企业要素、人脸实名等功能，并持续维护接口稳定性和查询体验。部分功能采用多线路、代理池自动切换机制，遇到线路异常会自动尝试可用节点，减少等待和失败情况。 🤖 机器人特点 多种核验功能集中使用 操作简单，按照指令提交即可 查询结果清晰直观 API 多线路自动切换 每日额度体系 邀请好友可获得额外额度 支持充值增加固定额度 人工客服协助处理使用问题 功能持续更新维护 ⚖️ 李律核验机器人 …
Channel created
Showing the 2 most recent of 2 posts we hold for @lilvhy. 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.
Named by 4 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.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“李律核验助手bot通知频道” (@lilvhy), 826 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/lilvhy.
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.