部分业务 降价 微信提取好友 😀😀😀😃 开房同居五年 😀😀😃😃 京东地址 😃😀😀 个人所得税 😃😀 微信反实名 😀😀 抖音反实名 😀😀 名下抖音 小红书 快手 网易云 😃😃

Channel
永盛天眼官方社工库通知
@yssgktyc
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
13,773subscribers
+3,192 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1004387097696 |
|---|---|
| Type | Channel |
| Username | @yssgktyc |
| Created | Between 1 June 2026 and 11 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/yssgktyc |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 19 Sept 2026, 17:38 | 13,773 | +198 |
| 17 Sept 2026, 07:18 | 13,575 | +182 |
| 15 Sept 2026, 08:18 | 13,393 | +117 |
| 13 Sept 2026, 13:56 | 13,276 | +46 |
| 11 Sept 2026, 20:22 | 13,230 | +182 |
| 9 Sept 2026, 07:17 | 13,048 | +285 |
| 5 Sept 2026, 21:59 | 12,763 | +178 |
| 3 Sept 2026, 19:16 | 12,585 | +114 |
| 2 Sept 2026, 11:24 | 12,471 | +72 |
| 1 Sept 2026, 13:38 | 12,399 | +48 |
| 31 Aug 2026, 17:13 | 12,351 | +155 |
| 30 Aug 2026, 15:32 | 12,196 | +104 |
| 29 Aug 2026, 13:05 | 12,092 | +141 |
| 28 Aug 2026, 12:04 | 11,951 | +114 |
| 27 Aug 2026, 14:16 | 11,837 | +90 |
| 26 Aug 2026, 13:21 | 11,747 | +169 |
| 25 Aug 2026, 13:35 | 11,578 | +189 |
| 24 Aug 2026, 10:04 | 11,389 | +294 |
| 22 Aug 2026, 21:04 | 11,095 | +147 |
| 21 Aug 2026, 13:04 | 10,948 | first reading |
Engagement
72 posts held, back to 11 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 28 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.37%
- avg views ÷ 13,773 subscribers
- Avg views / post
- 1,150
- 41 posts measured
- Reaction rate
- 0.107%
- reactions ÷ views · ER floor
- Posts in window
- 41
- of 72 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 18 of 41 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 72 (11 August 2026 – 2 September 2026) |
| Views total | 47,253 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 21:42 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
31 reactions across 25 posts, in 2 distinct kinds. The most used accounts for 61.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 61.3% | |
| ❤ | 12 | 38.7% |
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 27 of the 72 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 31 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 72 most recent posts we hold, published 11 August 2026 to 2 September 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
房产回完 已慢慢稳定 继续上 全国房产开 批量拿优势 首套 😀😃😃 后续每套套 😃😃 1-3工作日回单 空不收费 不可排除车位宅基地 可指定要多少他做 无遗漏 支持埋雷 随时涨价 唯一真单能回的路线 别再外面碰运气了 能给你的只有靠谱!
👍1
一年内美团外卖地址 最新10条 只要手机号报单 一年内记录保真不保漏) 带时间➕地址 每天限量,牛逼渠道, 手机号报单,美团的跑腿,闪送都出 都是保真不保漏,一条也收,敏感收费不回
👍1
无盲经侦流水回单 继续收 一月 😃😀😃 三月 😃😃😃 半年 😃😀😃 一年 😀😃😃 两年 😀😃😃 三年 😃😃😃 开卡 😃😀😃 上线8000或9999 可接指定 周四早上提交 周五回 满100单发车 代理拿优势
✨诉前资产调查大礼包:😀😃😃😃 ✨出名下以下银行,所有开卡流水 ✨工商银行✨农业银行✨中国银行 ✨建设银行✨中信银行✨光大银行 ✨华夏银行✨民生银行✨邮储银行 ✨交通银行✨浦发银行✨广发银行 ✨招商银行✨平安银行✨兴业银行 ✨渤海银行✨浙商银行✨恒丰银行 ✨出登记的不动产,房,矿,宅基地 ✨出全国工商登记,包括持股 ✨出最近5年,航班铁路信息包括同行 ✨明天发车,周一回单
找人业务整合 🥇 手机定位 ❤️❤️❤️❤️☹️ 手机轨迹 ❤️❤️❤️☹️ 真美团地址 ❤️❤️❤️❤️☹️ 高铁火车记录 ❤️❤️❤️☹️ 出入境记录 ❤️❤️❤️☹️ 京东地址 ❤️❤️❤️☹️ 水电地址 ❤️❤️❤️☹️ 常用地址 ❤️❤️❤️☹️ 邮政地址 ❤️❤️❤️☹️ 美团历史 ❤️❤️❤️☹️ 拼多多地址 ❤️❤️❤️☹️ 以上所有业务均支持 人民币u 担保交易
名下财产系列 名下银行卡 ❤️❤️❤️ 名下银行卡带余额 ❤️❤️❤️❤️ 名下车 ❤️❤️❤️ 全国名下房产 ❤️❤️❤️❤️ 地区名下房产 ❤️❤️❤️ 银行卡流水 ❤️❤️❤️❤️ 个税带工资收入 ❤️❤️❤️ 人行征信报告 ❤️❤️❤️❤️ 以上所有业务均支持 人民币u 担保交易
残血网逃 😃😀😀 带撤销 无详情 速度快 一天多批!
微信支付宝流水回完 微信流水 不带ID 支付宝流水 带ID 一月 😃😃😃 三月 😀😃😃 工作日1-3天回 来个小批量谈价格 要15单 要么全部微信 要么全部支付宝 能包的来
👍2
2个线路全部晚上发车 代理拿优势 线路1:无盲个户经侦流水降价收 一月 😃😀😃 三月 😃😃😃 半年 😃😀😃 一年 😀😃😃 两年 😀😃😃 三年 😃😃😃 开卡 😃😀😃 上线8000或9999 可接指定 周末晚上12点发车 3-5左右回 ——————————————— 流水线路2:柜台个户公户开卡流水 个人开卡 😀😃😃 公司开卡 😃😃😃 柜台开卡流水 建设银行 农业银行 招商银行 交通银行 工商银行 民生银行 平安银行 只要这些银行 空不收费、其他有任何数据都收费、 公户私户均无遗漏 无条数上限 公户(城投、融资、小贷、上市公司、国企、国企参股) 不要报,敏感扣单 周末发车3-7个工作日左右回 ———————————————
平替犯罪记录(全网最好的板子) 项目名称:个人判决书(犯罪记录) 个人判决书(犯罪记录)未公开也有 ‼️集犯罪记录✅ ‼️被执行详细✅ (刑事案情一样出) 😀😃😀 民事+刑事,人在就秒,当天回 注意⚠️系统有啥给啥,有的没有案件详情,刑事案件可能只有罪名没有判决结果能接受的报⚠️(刑事案件概率出判决结果) (版本很多,给你最好的板子) 以后报犯罪记录都来出这个,不要出服刑记录了,好用不贵
四网宽带地址 😃😀😀 带户号 带地址 带缴费单位 可指定地区指定运营商带入网时间 每天下午2点一直开秒!!!
Showing the 12 most recent of 72 posts we hold for @yssgktyc. 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.
Posts edited after publishing
@yssgktyc edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 26 August 2026
- Most recent edit
- 28 August 2026
Mentions
Named by 8 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“永盛天眼官方社工库通知” (@yssgktyc), 13,773 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/yssgktyc.
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.