出售无限制三要素独家无遗漏 支持发数据测试带录屏 @congrao 连最近新办的都可以核验偶

Channel
夜太冷
@HJ8906
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
11subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002223103901 |
|---|---|
| Type | Channel |
| Username | @HJ8906 |
| Created | 30 August 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 8 October 2026 |
| On Telegram | t.me/HJ8906 |
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 23:05 | 11 | -1 |
| 12 Aug 2026, 05:45 | 12 | no change |
| 7 Aug 2026, 14:01 | 12 | first reading |
Engagement
10 posts held, back to 30 August 2024 — 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 10 posts for this entry, the most recent from 30 November 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
7 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤮 | 3 | 42.9% | |
| ❤ | 2 | 28.6% | |
| 🔥 | 1 | 14.3% | |
| 🥰 | 1 | 14.3% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 3 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 30 August 2024 to 30 November 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
出售此微信破解姓名带质保20u 不带15u @congrao 支持春江等知名担保 非市面泛滥
假地址1u 7人民币一直在 @congrao
Channel photo removed
出售银行卡四要素(预留) 银行卡三要素(卡反) 以及二要素补齐4~5位 法人四要素 (可以核验异常及个体) 均为无限制百线程 支持任何形式的测试支持春江有需要的带价来问 @congrao
出一份无限制批量三要素支持 25u 支持春江 @congrao 无遗漏
业务 支机3u 机主4u 电百 14u 文字全户17u 破解人脸3u 卡反3u 网易云反 码反 口反 6u 汇率按7来算 批量可谈支持春江 支持 📱📱 支付宝 u 联系 @nb9068 除以上别的业务也来问
🤮3❤1🔥1🥰1
Channel name was changed to «旧时代»
出售 +592 6654299 +687 776233 每个35 联系 @congrao 😭🥹
❤1
Channel created
Showing the 10 most recent of 10 posts we hold for @HJ8906. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@HJ8906 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“夜太冷” (@HJ8906), 11 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/HJ8906.
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.