🎊金秋九月,硕果盈枝🚀 感谢您一直以来对「永盛」的信任与支持。 愿新的九月, 愿您生意兴隆、财源广进, 所行皆坦途,所求皆如愿, 事业蒸蒸日上,生活顺遂安宁。 新的月份,我们也将继续秉持专业、稳定、负责的态度, 为每一份信任提供更好的服务。

Channel
永盛社工库官方频道|官方公示
@yssgkgf
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
13,284subscribers
+3,091 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001641484442 |
|---|---|
| Type | Channel |
| Username | @yssgkgf |
| Created | 24 August 2022 — measured — dated from the channel’s first post |
| First recorded | 23 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/yssgkgf |
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 95% 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, 14:16 | 13,284 | +225 |
| 17 Sept 2026, 03:58 | 13,059 | +179 |
| 15 Sept 2026, 05:39 | 12,880 | +133 |
| 13 Sept 2026, 17:56 | 12,747 | +54 |
| 11 Sept 2026, 22:17 | 12,693 | +159 |
| 9 Sept 2026, 13:58 | 12,534 | +291 |
| 6 Sept 2026, 03:41 | 12,243 | +283 |
| 3 Sept 2026, 22:37 | 11,960 | +101 |
| 2 Sept 2026, 16:05 | 11,859 | +91 |
| 1 Sept 2026, 14:58 | 11,768 | +97 |
| 31 Aug 2026, 14:44 | 11,671 | +144 |
| 30 Aug 2026, 17:48 | 11,527 | +143 |
| 29 Aug 2026, 19:16 | 11,384 | +151 |
| 28 Aug 2026, 17:04 | 11,233 | +152 |
| 27 Aug 2026, 20:08 | 11,081 | +164 |
| 26 Aug 2026, 17:13 | 10,917 | +207 |
| 25 Aug 2026, 14:23 | 10,710 | +265 |
| 24 Aug 2026, 13:53 | 10,445 | +252 |
| 23 Aug 2026, 19:00 | 10,193 | no change |
| 23 Aug 2026, 18:45 | 10,193 | first reading |
Engagement
9 posts held, back to 24 August 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 16 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 41.5%
- avg views ÷ 13,284 subscribers
- Avg views / post
- 5,510
- 3 posts measured
- Reaction rate
- 0.058%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 9 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 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 9 (24 August 2022 – 1 September 2026) |
| Views total | 16,530 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 23:35 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
5 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 80.0% | |
| 👍 | 1 | 20.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 3 of the 9 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 24 August 2022 to 1 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
永盛新押10万U公群 总押二十多万 U 交易有保障 欧易担保 @oedb 上押 10 万 U 公群1 https://t.me/+0Z88L6LWi70zYjZl ☀️🎆永盛天眼 查档专家🎆 🔥🔥公群上押188888u 🔥🔥 公群2 https://t.me/+BowVaqV1pXkxY2I1 全网担保上押超百万资金 交易有保障 以上只是其中一个公群 更多公群请联系官方客服查看 官方通知频道 @yssgkgf 防失联备用频道 @ysfslpd 高级调查频道 @yssgktyc 付费天眼备用频道 @yuantouchad 社工库通知频道 @yssgkmfcha 网红曝光频道 @yswhbg 🚀官方指定客服(官方永盛客服) 🚀永盛客服:@zgrboos
☀️🎆永盛天眼 查档专家🎆 🔥🔥公群上押188888u 🔥🔥 https://t.me/+BowVaqV1pXkxY2I1 全网担保上押超百万资金 交易有保障 以上只是其中一个公群 更多公群请联系官方客服查看 官方通知频道 @yssgkgf 防失联备用频道 @ysfslpd 高级调查频道 @yssgktyc 付费天眼备用频道 @yuantouchad 社工库通知频道 @yssgkmfcha 网红曝光频道 @yswhbg 🚀官方指定客服(官方永盛客服) 🚀永盛客服:@zgrboos
❤2👍1
⚠️外面骗子横行,谨防各种套路!⚠️ 市场鱼龙混杂,各种套路层出不穷: 👎 先交押金 👎 查完再收解密费 👎 签所谓保密协议才能查看 👎 查询过程中不断加价 👎 查不到不退款 👎 低价引流,后续层层收费 ➡️感谢你选择【永盛天眼】。 🔥我们始终坚持公开、透明、诚信的服务原则: ✔️全程无押金 ✔️全程无套路 ✔️无解密费 ✔️无保密协议 ✔️无任何隐形收费 ✔️明码标价,价格透明 ✔️查前确认,查后不加价 ⭐️ 在这里,你不用担心被套路,也不用担心临时加价。 ⭐️ 选择永盛天眼,就是选择一份安心与信任。 ⭐️ 永盛天眼|诚信经营,用实力赢得信任。 公群已上押 私信拿链接 🚀官方指定客服(官方永盛客服) 🚀永盛客服:@zgrboos
❤1
⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️ 点击我查看所有模板 点击我查看所有模板 点击我查看所有模板 公群已上押 私信可以找我拿链接 🚀官方指定客服(官方永盛客服) 🚀永盛客服:@zgrboos
Channel name was changed to «22»
🆘紧急通知!!!! 近期有众多诈骗分子向机器人投放恶意广告切勿相信 与上图片相似 带有 Ad 广告 等字样 任何出现在对话框顶部、带有[Ad]或[广告]标识的内容,均为Telegram官方广告平台自动推送的竞价广告,与上帝之眼运营方无关联 无法保证交易安全 维权方式(如果被骗) 机器人最上面标有“赞助”的广告消息,长按该消息(或者点击右上角三个点)。(如果您已被骗) 请选择以下选项维权 1.选择倒数第三个:Copyright infringement 侵犯版权或者盗版 2.然后第一个选项是(Piracy or )盗版和侵犯版权 第二个是冒充(Impersonation)(根据情况选择!) 3.然后所有四个选项都是这个 The ad (文字) The destination(机器人和通道)The product(产品或者服务)Everything(一切) (自行选择) 😀请无理由相信永盛天眼 🚀官方指定客服(官方永盛客服) …
❤1
📱 永盛品牌矩阵|唯一官方 · 权威公示 为防止仿冒、混淆与恶意引流,现对上帝之眼体系内所有官方入口、频道与信用标识统一公示如下: ✈️官方机器人入口 免费天眼查机器人 @yssgmfchabot 🌐 官方频道矩阵 官方通知频道 @yssgkgf 防失联备用频道 @ysfslpd 高级调查频道 @yssgktyc 付费天眼备用频道 @yuantouchad 社工库通知频道 @yssgkmfcha 网红曝光频道 @yswhbg 🚀官方指定唯一客服 @zgrboos @gp520 两个用户名都为同一个人 🌐官方承诺与品牌说明 永盛坚持长期运营与清晰边界, 所有官方入口、频道、客服与生态关系统一公示、可验证。 我们不制造信息焦虑, 不依赖私下引导建立信任。 一切以公开、公示、权威发布为准。 本公示为当前唯一官方参考版本, 后续如有任何调整, 仅通过官方通知频道或官方备用频道发布。 🔓以上账号、频道、入口及编…
Channel created
Showing the 9 most recent of 9 posts we hold for @yssgkgf. 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
@yssgkgf edited 1 post 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
- 24 August 2026
- Most recent edit
- 24 August 2026
Mentions
Named by 1 registered channel — 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.
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.
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.
“永盛社工库官方频道|官方公示” (@yssgkgf), 13,284 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/yssgkgf.
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.