既然被挖了 就泛滥吧 赶紧给它艹死 接码一次码token 5小时过期 你离绪哥 ad 较真 #假地址 #青岛 #脚本 --@zeroc0 ——匿名 📮 投稿通道 ☘️ 交流群组
👍1

Channel
@fen520xiang
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
4,964subscribers
-9,077 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001013775551 |
|---|---|
| Type | Channel |
| Username | @fen520xiang |
| Created | Between 1 December 2015 and 31 March 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 46 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/fen520xiang |
Other / unclassifiable — 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 65% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 02:50 | 4,964 | -697 |
| 14 Nov 2026, 08:06 | 5,661 | -871 |
| 9 Nov 2026, 09:14 | 6,532 | -506 |
| 6 Nov 2026, 09:39 | 7,038 | -292 |
| 3 Nov 2026, 00:09 | 7,330 | -233 |
| 30 Oct 2026, 19:06 | 7,563 | -507 |
| 27 Oct 2026, 19:26 | 8,070 | -317 |
| 25 Oct 2026, 05:36 | 8,387 | -394 |
| 22 Oct 2026, 10:45 | 8,781 | -559 |
| 18 Oct 2026, 17:37 | 9,340 | -624 |
| 15 Oct 2026, 17:26 | 9,964 | -245 |
| 14 Oct 2026, 20:35 | 10,209 | -284 |
| 13 Oct 2026, 15:37 | 10,493 | -485 |
| 9 Oct 2026, 16:55 | 10,978 | -530 |
| 5 Oct 2026, 07:58 | 11,508 | +1,606 |
| 26 Sept 2026, 15:16 | 9,902 | -1,684 |
| 19 Sept 2026, 16:00 | 11,586 | -745 |
| 17 Sept 2026, 03:40 | 12,331 | -563 |
| 15 Sept 2026, 01:39 | 12,894 | -251 |
| 13 Sept 2026, 11:38 | 13,145 | first reading |
79 posts held, back to 29 July 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 46 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 2 November 2026 |
|---|---|
| Posts held | 79 (29 July 2026 – 2 November 2026) |
| Views total | 1,280 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 12:01 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.
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
411 reactions across 67 posts, in 22 distinct kinds. The most used accounts for 38.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 157 | 38.2% | |
| 👍 | 96 | 23.4% | |
| 🤮 | 24 | 5.84% | |
| 👎 | 18 | 4.38% | |
| 💩 | 18 | 4.38% | |
| 🤔 | 16 | 3.89% | |
| 🤣 | 16 | 3.89% | |
| 🤯 | 12 | 2.92% | |
| 🥰 | 10 | 2.43% | |
| 👏 | 9 | 2.19% | |
| 🔥 | 8 | 1.95% | |
| 😱 | 5 | 1.22% | |
| 🌭 | 4 | 0.973% | |
| 💋 | 4 | 0.973% | |
| 🙏 | 3 | 0.73% | |
| 🤨 | 3 | 0.73% | |
| 😁 | 2 | 0.487% | |
| 🤬 | 2 | 0.487% | |
| 🍓 | 1 | 0.243% | |
| 🖕 | 1 | 0.243% | |
| 2 further kinds | 2 | 0.487% |
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 68 of the 79 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 411 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 79 most recent posts we hold, published 29 July 2026 to 2 November 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.
Telegram’s own ‘edited’ marker: 1 of 3 posts held from the last 30 days (33.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
既然被挖了 就泛滥吧 赶紧给它艹死 接码一次码token 5小时过期 你离绪哥 ad 较真 #假地址 #青岛 #脚本 --@zeroc0 ——匿名 📮 投稿通道 ☘️ 交流群组
👍1
#小程序://天府银行/q29u02dt6pyiL4g {"code":"0","message":"SUCCESS","data":{"cifseq":null,"map":{"returnCode":"0431","custno":null,"returnMsg":"[0431]查询证件类型[居民身份证:109010001],证件号码[511302197807255728],客户姓名[王朝霞]对应的客户记录失败,无对应记录","etcsnm":null,"etcdnm":null,"onacnm":null,"brchno":null,"mobitl":null,"idtftp":null}}} 【 "mobitl" : null, // 预留手机号】 --@zeroc0 ——匿名 📮 投稿通道 ☘️ 交流群组
👍1
二要素核验自行替换tk,可以核验敏感+14岁以下 ——@xbfhn 📮 投稿通道 ☘️ 交流群组
❤1
迷你世界存储桶没关好支付源码和内部代码直接裸奔GM后台地址也漏了 最近发现迷你世界官网的一个静态资源站点web-static.mini1.cn它的存储桶只要输入网址,能直接把里面的文件列表全拉出来还能随意下载 支付宝的源码包有一个叫 alipay.trade.wap.pay-java-utf-8.zip的文件是支付宝手机网站支付的后台代码里面带着真的商户密钥能伪造充值白嫖迷你币 还有一堆内部后台代码有个叫 hermes 的文件夹,里面全是创作者中心、开发者后台还有秒开Web的各个版本打包文件,连以前的 .git 历史记录都在里面。还有抽奖和兑换模板还找到了exchange-template.xlsx(兑换)和 lucky-template.xlsx(抽奖)的表格文件,里面估计有接口怎么传参数的格式。 并且还发现了迷你世界的GM后台登录地址gm.minifire.cn不过是内网地址有能力的自己研究 ——匿名 📮 投稿通…
👍3❤1
石嘴山银行全国头 7.30-19.30 ——匿名 📮 投稿通道 ☘️ 交流群组
🤨3❤1👍1
微信小程序-墨脱 · 万国足道-我的-注册-随便输入手机号抓包-点最大那个包的响应-解密-自定义短信-可自定义文字 大化瑶族自治县人民医院智慧医院-自定义短信自己研究 ——匿名 📮 投稿通道 ☘️ 交流群组
👍7👎2
河北人社 社会保障卡 亲情账户维护 添加 重置社保密码 刷人脸 抓包过不去 https://www.sjz12333.net/ywtb/#/registerOne 打开 个人登录 找回密码 输入二要素 社保卡号需要补齐 社保密码 重置 密码 然后石家庄人社登录 就业创业抓包找 https://www.sjz12333.net/ggfw/config/message.json?access_token=23a9e3b0-3c7a-42ac-bb78-8d8266802104 这个 然后手动输入py 输入身份证 自动下载社保头带地址 ——匿名 📮 投稿通道 ☘️ 交流群组
👍6
河北人社 社会保障卡 亲情账户维护 添加 重置社保密码 刷人脸 抓包过不去 https://www.sjz12333.net/ywtb/#/registerOne 打开 个人登录 找回密码 输入二要素 社保卡号需要补齐 社保密码 重置 密码 然后石家庄人社登录 就业创业抓包找 https://www.sjz12333.net/ggfw/config/message.json?access_token=23a9e3b0-3c7a-42ac-bb78-8d8266802104 这个 然后手动输入py 输入身份证 自动下载社保头带地址 ——匿名 📮 投稿通道 ☘️ 交流群组
👍6
天津全自动全名下脚本(包含房产) 内置豪猪和云码版本和手动输入验证码 房产思路: 全自动改完密码手动登录津心办,点击主页津心登看我的证件 爱来自Er 小r 云凤 ——@Erebus466 📮 投稿通道 ☘️ 交流群组
👍6
江西神父+江西社保详细信息 全自动脚本 填入江西政务网账号即可使用 爱来自Er以及云风 ——@Erebus466 📮 投稿通道 ☘️ 交流群组
👍6
批量三要素 有点垃圾 核验成功之后可无限制核验 可以四网 ——匿名 📮 投稿通道 ☘️ 交流群组
👍2
概率V2有限制核验口 需要用户关注微信支付商家助手公众号 https://pay.weixin.qq.com/index.php/extend/staff_account 员工管理 - 新增员工账号 - 输入姓名和微信号即可核验 { "errorcode": -124, "msg": "微信用户没有关注公众号", "data": { "nickname": "政", "portrait_url": "http://wx.qlogo.cn/mmhead/16OvUZfwjeQGo45UeN5TviaOJqnN4cYRrYa4hyIibpQ7K2qJiaJvBpPx6ndlhczGwSe9W3WSMCYv4E/64/0" } } { "errorcode": -126, "msg": "实名不一致 <div class='tips-info'>员…
👍6
Showing the 12 most recent of 79 posts we hold for @fen520xiang. 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.
We recorded 4 posts on @fen520xiang as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“X分享” (@fen520xiang), 4,964 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/fen520xiang.
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.