Telegram RegisterThe public register of Telegram
Telegram profile photo for TY社工库通知群

Channel

TY社工库通知群

@TYsgk888

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

150subscribers

-17 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002417332708
TypeChannel
Username@TYsgk888
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live27 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/TYsgk888

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 25 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 the other topics.

Growth

1491691599 August 2026 — 167 subscribers10 August 2026 — 167 subscribers18 August 2026 — 168 subscribers25 August 2026 — 169 subscribers31 August 2026 — 167 subscribers10 September 2026 — 165 subscribers18 September 2026 — 166 subscribers4 October 2026 — 159 subscribers13 October 2026 — 149 subscribers27 October 2026 — 150 subscribers1509 August 202627 October 2026
10 measurements spanning 79 days, net -17. 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 146–172 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Oct 2026, 11:55150+1
13 Oct 2026, 16:18149-10
4 Oct 2026, 01:56159-7
18 Sept 2026, 16:19166+1
10 Sept 2026, 01:57165-2
31 Aug 2026, 17:08167-2
25 Aug 2026, 16:53169+1
18 Aug 2026, 09:12168+1
10 Aug 2026, 13:57167no change
9 Aug 2026, 20:45167first reading

Engagement

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

Reaction mix

23 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 73.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1773.9%
🤮313.0%
💩28.70%
👍14.35%

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 8 of the 20 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 July 2025 to 20 September 2025, 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

20 Sept 2025, 02:12 UTC189 views1 reactionsread 9 August 2026

TY社工库经过长久沉寂,现已卷土归来💪💪💪

❤1

8 Aug 2025, 13:46 UTC327 viewsread 9 August 2026

看到很多人问 TY社工库为何不回复了 原因:我们在升级UI 有很多人抱怨 说看不懂这个面板 经过团队内深思熟虑 觉得应该进行改良 本次改良预计12h内完工 ——TY工作室

4 Aug 2025, 15:00 UTC631 views7 reactionsread 9 August 2026

我们修复了机器人的BUG 原因:因为免费七天 我们的使用量达到了每天5w次+,这是我们团队都没想到的,现在已经更换更新的服务器,并且给家人们补了两天会员 下次更新预计:增加红包系统 我们将发送价值1888USDT的机器人积分 成神之路,你与我共勉 敬请期待......... TY集团

❤3🤮3👍1

1 Aug 2025, 08:16 UTC364 views4 reactionsread 9 August 2026

免费查询已开启,七天内所有查询功能无需任何积分

❤2💩2

1 Aug 2025, 08:15 UTC340 viewsread 9 August 2026

✅ 已开启免费查询 开始时间: 2025-08-01 16:15:16 结束时间: 2025-08-08 16:15:16 在接下来的 7 天内,所有查询功能免费! 🎉 所有用户无需积分即可使用查询服务

1 Aug 2025, 07:53 UTC298 viewsread 9 August 2026

由于机器人数据更新,导致短暂性的不可用,请在十分钟后重新发送查询信息,如果您联系客服 @AYueTYBot 长时间没有得到回复,请再次发送信息

1 Aug 2025, 05:05 UTC294 viewsread 9 August 2026

有人问客服 有没有好看的看片频道? TY客服为了满足大众需求 建立了一个频道,里面会收录TY员工们喜欢看的高质量片子,也可以投稿你喜欢看的,供大家欣赏 频道 https://t.me/TYhuangpian

31 Jul 2025, 07:27 UTC238 viewsread 9 August 2026

已恢复所有功能 客服为 @AYueTYBot 有任何需求服务请联系客服

31 Jul 2025, 07:10 UTC226 viewsread 9 August 2026

各位稍安勿躁,为了保证机器人的稳定运行,数据正在迁移至新的服务器,预计更新时长30分钟

28 Jul 2025, 15:34 UTC660 views5 reactionsread 9 August 2026

@TYmxhBot TY工作室出品的名下号机器人 自助报单 回单速度快 ! 购买积分: @AYueTYBot

❤5

27 Jul 2025, 14:57 UTC231 views1 reactionsread 9 August 2026
Photo

客服一直在 但是请不要发这些一点用都没有的信息!!!

❤1

Showing the 12 most recent of 20 posts we hold for @TYsgk888. 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 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 27 October 2026 — this entry's latest reading, not the date you are reading this.

“TY社工库通知群” (@TYsgk888), 150 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/TYsgk888.

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.