Channel
@FreeSGK520
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
34,211subscribers
-336 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001796278567 |
|---|---|
| Type | Channel |
| Username | @FreeSGK520 |
| Description | 免费社工库机器人: @sgk520_bot 免费匿名网盘机器人: @wangpan_bot 网盘资源频道: @wjgxpan 大象索引 - 搜索神器: @DaXiangIndexBot 加密货币钱包交易及钱包信息查询: 查币机 @chabijiwbot 电子书机器人: 电子图书搜索机器人 @dianzishuwubot 客来啦精准获客机器人: 拓客机器人 @kelailabot |
| Created | Between 1 January 2022 and 17 July 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/FreeSGK520 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 23:58 | 34,211 | -26 |
| 20 Aug 2026, 16:15 | 34,237 | -10 |
| 19 Aug 2026, 14:22 | 34,247 | -27 |
| 18 Aug 2026, 13:33 | 34,274 | -36 |
| 17 Aug 2026, 14:17 | 34,310 | -34 |
| 16 Aug 2026, 07:23 | 34,344 | -40 |
| 14 Aug 2026, 19:24 | 34,384 | -25 |
| 13 Aug 2026, 09:57 | 34,409 | -18 |
| 12 Aug 2026, 12:24 | 34,427 | -30 |
| 11 Aug 2026, 10:57 | 34,457 | -23 |
| 10 Aug 2026, 11:01 | 34,480 | -29 |
| 9 Aug 2026, 07:52 | 34,509 | -29 |
| 8 Aug 2026, 08:27 | 34,538 | -9 |
| 7 Aug 2026, 12:30 | 34,547 | no change |
| 7 Aug 2026, 12:21 | 34,547 | first reading |
18 posts held, back to 17 July 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 34 pagesof 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 7 December 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
【新产品】2023.03.16 ChatGPT聊天机器人及一键去除图片背景: @typingmindbot 转发消息备份机器人: 转发消息备份机器人 @messagesaver520bot 1.【100美金】whatsapp全球5亿+用户手机号【中国手机号70万条左右】 类型:出售 价格:100USDT 详情:👉点击查看 2.【100美金】全球推特数据2亿+ 类型:出售 价格:100USDT 详情:👉点击查看 3.【500美金】全球领英数据7亿+ 类型:出售 价格:500USDT 详情:👉点击查看 4.【500美金】电动汽车用户数据1500万+ 类型:出售 价格:500USDT 详情:👉点击查看 5.【100美金】美国4亿选民数据 类型:出售 价格:100USDT 详情:👉点击查看 6.【20美金】希尔顿酒店数据370万记录 类型:出售 价格:20USDT 详情:👉点击查看 7.【100美…
拓客机器人:【支持会员试用】 2022.12.31 新产品 “客来啦” @kelailabot 帮助文档: 👉查看 30U 永久会员 30U 永久会员 30U 永久会员 给您带来可能是数千美金的收益！ 【问题】 单量少： 销量业绩上不去❓ 广告、促销做了不少，但效果却平平！😭😭 客流少： 开拓新客拿不准❓ 开拓新客花不少钱，找不到精准客群！😢😢 【解决方案】 「客来啦机器人」获客新方式，帮助您精准且高效获取潜在客户！👍👍 👉 👉 @kelailabot 【客来啦机器人】如何帮我找精准客户呢？ 【客来啦机器人】通过对多个优秀群组关键词监测，协助您精准筛选潜在客户。 有了【客来啦机器人】，您将能优雅且高效地主动获得您期望地客户群体，为此，您仅需付出少量报酬即可！ 来试试吧，新客可免费试用24小时 👉 👉 @kelailabot 导航群组搜索就好比一个大商场，客流很多…
社工库查询机器人新增功能: 1. 猎魔查询 条件: 月度会员 查询方式: 姓名 地区 比如:张三 黑龙江
产品矩阵: 我们只有以下群组及机器人，其他群组及机器人都是假号: 接收通知: 社工库群组(群组): @FreeSGK520 网盘机器人群组(群组): @wjgxpan 社工库查询: 社工库查询(机器人): @sgk520_bot 帮助文档: 👉查看 网盘、观看视频【几百万部优质视频资源】、听音乐【待上线】: 网盘机器人(机器人): @wangpan_bot 电报群组、电报群关系查询： 频道、群组搜索机器人 大象超级索引(机器人) @DaXiangIndexBot 帮助文档: 👉查看 加密货币钱包交易及钱包信息查询: 查币机 @chabijiwbot 电子书机器人: 电子图书搜索机器人 @dianzishuwubot 帮助文档: 👉查看 拓客机器人: 拓客机器人 @kelailabot 帮助文档: 👉查看 钱包监控机器人: 钱包监控机器人 @qianbaojiankongbot 数据交易平台: 数据交易平台:…
大家都知道国内下载的电报客户端可能会篡改钱包地址 如果通过web登录就可以确保钱包地址无法被篡改 电报网页端登录地址如截图中所示 https://web.telegram.org 多些细心 就不会出现转账错误 如果发现链接和截图不一样 不要点击链接 诈骗电报客户端昨天才创建的诈骗钱包 短短一天时间就诈骗8万多元 资产信息如下: 钱包:TPfeTY5uB7EqurpKWmvdcSwxzExH7X3QGV 总价值:12552.386600U(¥81590.51290119984)(trx: 236735.703379) 查询时间:2022/11/27 10:22:01 数据查询来自查币机: https://t.me/chabijiwbot
社工库群组 pinned «【2022.11.15 更新】 电报诈骗app其中一个钱包目前已经有累计(转入) 400多万资金 钱包:TF9HGEMDp4BjF9obBnXwqj7wJzaq1hZ8iq 如需查询具体钱包信息 点击 查币机 https://t.me/chabijiwbot 币安账户: TKoMsfXd3E9joLVjJnSc59wXgh8LZSwApy TEi6ChrKe7KR2kKbEgBHZAqLcCEM9vZUne 结合其他电报群信息: 诈骗电报客户端通过接口获取钱包地址，骗子申请的域名疑似为 haottgg.com…»
【2022.11.15 更新】 电报诈骗app其中一个钱包目前已经有累计(转入) 400多万资金 钱包:TF9HGEMDp4BjF9obBnXwqj7wJzaq1hZ8iq 如需查询具体钱包信息 点击 查币机 https://t.me/chabijiwbot 币安账户: TKoMsfXd3E9joLVjJnSc59wXgh8LZSwApy TEi6ChrKe7KR2kKbEgBHZAqLcCEM9vZUne 结合其他电报群信息: 诈骗电报客户端通过接口获取钱包地址，骗子申请的域名疑似为 haottgg.com 域名创建时间: 2022年07月17日 注册商: GoDaddy 转账之前一定反复截图确认转账钱包信息 ！！！ 转账之前一定反复截图确认转账钱包信息 ！！！ 转账之前一定反复截图确认转账钱包信息 ！！！ 诈骗钱包地址列表(继续扩充中): TFqHAzWj6RpmwxhSnCdCMYR4qk4ExGYV9E TVfW…
👉👉 一位被骗了3万美金！！！ 大家如果继续使用国内下载的客户端 就等着被骗吧 图1中是假的TG客户端看到的钱包地址 图2是正确的地址 我已经将诈骗客户端的钱包地址进行整理分析 背后的骗子会受到法律制裁！ 已经诈骗数十万甚至百万！ 诈骗钱包地址列表(继续扩充中): TFqHAzWj6RpmwxhSnCdCMYR4qk4ExGYV9E TVfWc7rHaCYGGbYgo7TZ8WFMPeersokSHa TCoruSv7M6816biGj4VeCtcBNJo8w6d8iK TYZnANzomVTLN6JjkyiimUhnQ5X1rUgibq TFCJxhX4EgiW2VW3hsoUrDCa8mCmEKV5AH TKbeKAUoyH8jMTxZeSHSaX3zmdmLjFKVke TN2rmWcVeisPFFHDEN7z6swR67mb4S4KJu TKHzSYJdgNFyxktT5HGmcUq44v8AgHzorL TJH4…
【新产品上线】2022.10.15 查币机器人 @chabijiwbot 查询加密货币钱包哦~ 查币机器人 @chabijiwbot 使用方法 国内电报客户端诈骗 诈骗钱包地址列表(继续扩充中): TFqHAzWj6RpmwxhSnCdCMYR4qk4ExGYV9E TVfWc7rHaCYGGbYgo7TZ8WFMPeersokSHa 摘取部分信息 一位被骗了1万美金 发送方:TM1zzNDZD2DPASbKcgdVoTYhfmYgtfwx9R【Okex 1】 接收方:TVfWc7rHaCYGGbYgo7TZ8WFMPeersokSHa 转账时间:2022/10/25 22:30:51 网络:trc20 状态:确认完成 数量:10000U【转入】【大额】(¥65000) 区块:45375681 使用国内电报客户端赶紧卸载！从正规渠道下载！！ 钱包数据查询支持来自 @chabijiwbot
国内钱包诈骗 案例1 国内电报客户端诈骗案例2 我们的产品如下(覆盖用户总数500w+🎈🎈🎈):
Showing the 12 most recent of 18 posts we hold for @FreeSGK520. 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.
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.
@FreeSGK520 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.
References a handle that is not a live channel — we have no record it ever was one.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“社工库群组” (@FreeSGK520), 34,211 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/FreeSGK520.
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.