https://t.me/ZhongQingJuSGK1BOT?start=8424964632 把此链接挂在主页积分可获得更多

Channel
哈希社工库查档频道
@HaXiSGK666
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,737subscribers
-42 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002777358969 |
|---|---|
| Type | Channel |
| Username | @HaXiSGK666 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/HaXiSGK666 |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 12 Oct 2026, 06:58 | 1,737 | -12 |
| 5 Oct 2026, 05:21 | 1,749 | -11 |
| 26 Sept 2026, 08:39 | 1,760 | -11 |
| 17 Sept 2026, 17:41 | 1,771 | -6 |
| 13 Sept 2026, 08:41 | 1,777 | -3 |
| 9 Sept 2026, 06:38 | 1,780 | +3 |
| 1 Sept 2026, 01:38 | 1,777 | -4 |
| 28 Aug 2026, 17:23 | 1,781 | +1 |
| 25 Aug 2026, 15:58 | 1,780 | -6 |
| 19 Aug 2026, 10:02 | 1,786 | -3 |
| 16 Aug 2026, 06:08 | 1,789 | +7 |
| 12 Aug 2026, 06:22 | 1,782 | +3 |
| 11 Aug 2026, 19:46 | 1,779 | first reading |
Engagement
18 posts held, back to 11 November 2025 — 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 18 posts for this entry, the most recent from 11 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
4 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.0% |
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 4 of the 18 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 11 November 2025 to 11 May 2026, 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
https://t.me/zhongqingjuSGK8
https://t.me/zhongqingjuSGK8
感谢老板支持充值会员👍
👍现在邀请好友使用以下特点 👍分享链接给好友或者群聊频道可以有什么作用😂 👍获得积分奖励翻倍积分作用用于查询大量数据✈️ 👍 使用机器人 @tianshiSGKbot 👍机器人客服 @tianshiSGK 👍双向私信客服 @tianshia_bot
有单子冲我来谢谢
一天最低量千起或者百起可以私信我我叫小瞳不要为难我的同行有单子请跟我合作谢谢我全天有空给老板出请各位老板多多为难我小瞳我不怕为难合作私信我 @xiaotongye
欢迎老板上压力量越多越好欢迎 律所催收法务合作 @xiaotongye
❤1
感谢老板信任👍
哈希社工库查档频道 pinned «❤️哈希社工库机器人❤️ 😂 @HaXiSGK_bot 😂 👍哈希社工库查询群💪 https://t.me/HaXiSGK7 👀哈希免费核验机器人😈 @HaXihybot 😠哈希免费核验查询群😎 https://t.me/httpsHaXiSGK9 👍 哈希大头机器人👍 ✈️ @HaXiDTBOT ✅ ⚡哈希大头社工库查询群⚡ https://t.me/HaXiSGK8 ✅ …»
❤️哈希社工库机器人❤️ 😂 @HaXiSGK_bot 😂 👍哈希社工库查询群💪 https://t.me/HaXiSGK7 👀哈希免费核验机器人😈 @HaXihybot 😠哈希免费核验查询群😎 https://t.me/httpsHaXiSGK9 👍 哈希大头机器人👍 ✈️ @HaXiDTBOT ✅ ⚡哈希大头社工库查询群⚡ https://t.me/HaXiSGK8 ✅ ✅ ✅
报单🈳会退
Showing the 12 most recent of 18 posts we hold for @HaXiSGK666. 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
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.
Handles this channel named that no longer answer
- Dead references
- 4
- 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
- 4
- vacant every time we have ever looked
@HaXiSGK666 named 4 handles 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 2 posts, 12 August 2026 – 12 August 2026
named in 2 posts, 12 August 2026 – 12 August 2026
named in 2 posts, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“哈希社工库查档频道” (@HaXiSGK666), 1,737 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/HaXiSGK666.
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.