Telegram RegisterThe public register of Telegram
Telegram profile photo for LH.tech【国卡通知】

Channel

LH.tech【国卡通知】

@ycyc12345

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

2,044subscribers

-617 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001710840732
TypeChannel
Username@ycyc12345
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live13 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/ycyc12345

Topic

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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

2,0442,6792,361.510 August 2026 — 2,661 subscribers11 August 2026 — 2,661 subscribers11 August 2026 — 2,663 subscribers15 August 2026 — 2,670 subscribers17 August 2026 — 2,673 subscribers21 August 2026 — 2,675 subscribers24 August 2026 — 2,679 subscribers2 September 2026 — 2,660 subscribers7 September 2026 — 2,640 subscribers11 September 2026 — 2,637 subscribers15 September 2026 — 2,631 subscribers19 September 2026 — 2,637 subscribers30 September 2026 — 2,051 subscribers7 October 2026 — 2,046 subscribers13 October 2026 — 2,044 subscribers10 August 202613 October 2026
15 measurements spanning 63 days, net -617. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,949–2,774 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 00:012,044-2
7 Oct 2026, 00:572,046-5
30 Sept 2026, 04:382,051-586
19 Sept 2026, 11:192,637+6
15 Sept 2026, 00:392,631-6
11 Sept 2026, 13:212,637-3
7 Sept 2026, 03:152,640-20
2 Sept 2026, 21:392,660-19
24 Aug 2026, 19:252,679+4
21 Aug 2026, 04:452,675+2
17 Aug 2026, 20:462,673+3
15 Aug 2026, 00:232,670+7
11 Aug 2026, 10:552,663+2
11 Aug 2026, 00:002,661no change
10 Aug 2026, 23:472,661first reading

Engagement

20 posts held, back to 29 July 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 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 13:56 UTC141 viewsread 11 August 2026
Photo

连信 一直死的 检查下 api等待时间 设置成100 有的60多的后面来的注册不上。不丢吗的检查 网络。现在恢复放卡

7 Aug 2026, 10:08 UTC201 viewsread 11 August 2026

小红书目前不开新户 老客没封的账户 可以充

6 Aug 2026, 06:00 UTC256 viewsread 11 August 2026
Photo

河马 数据差的时候就停一会 再做 数据好的时候都是正常 数据差的时候一直取 导致账户封禁 还在怪骂河马的 就说明河马不适合你 这种就不要买卡了

5 Aug 2026, 13:46 UTCviews —

LH.tech【国卡通知】 pinned «明日启动新网站 旧站点支付功能将关闭 晚点上架商品 下单前问我有没有卡 拦截自助下单»

5 Aug 2026, 11:33 UTC251 viewsread 11 August 2026
Photo

明天下午一点 新渠道陌陌首次上线 卡多回吗高 新卡多 无错码 价格低 寻跑量客户

5 Aug 2026, 02:42 UTC249 viewsread 11 August 2026

通道4⃣️陌陌首 卡商那边用的人多拉爆了 现在出卡慢 在更换机器 预计明天 后天恢复

3 Aug 2026, 10:35 UTC317 views0 reactionsread 11 August 2026

小红书目前不接 陌陌 灵魂最近卡多 要开可以来

Showing the 12 most recent of 20 posts we hold for @ycyc12345. 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.

Mentions

Named by 5 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.

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 13 October 2026 — this entry's latest reading, not the date you are reading this.

“LH.tech【国卡通知】” (@ycyc12345), 2,044 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/ycyc12345.

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.