Channel
@xiaonianfenxiang
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,467subscribers
+0 since we began measuring on 3 October 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004391772945 |
|---|---|
| Type | Channel |
| Username | @xiaonianfenxiang |
| Description | Python做為通用程式語言本身合法，可用於程式學習、數據分析、網站開發等正當用途。但嚴禁任何人利用Python撰寫爬蟲、查詢腳本從事人肉開盒、非法蒐集、竊取、販賣公民身分證、手機號、住址等個人隱私資訊。人肉開盒屬網路暴力與違法行為，觸犯侵犯公民個人資訊罪，輕者治安處罰，重者追究刑事責任。本群杜絕一切黑灰產技術交流，技術須恪守法律底線，切勿以身試法。 |
| Created | Between 1 June 2026 and 30 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 October 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/xiaonianfenxiang |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 20:22 | 1,467 | no change |
| 3 Oct 2026, 19:47 | 1,467 | first reading |
20 posts held, back to 30 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 1 page 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. It is computed over the 8 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 October 2026 |
|---|---|
| Posts held | 20 (30 August 2026 – 3 October 2026) |
| Views total | 2,362 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Oct 2026, 20:22 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.
Lifetime counters from Telegram’s own channel header, read 3 October 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.
20 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 40.0% | |
| 👍 | 8 | 40.0% | |
| 👀 | 1 | 5.00% | |
| 🔥 | 1 | 5.00% | |
| 🤩 | 1 | 5.00% | |
| 🥰 | 1 | 5.00% |
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 9 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 20 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 30 August 2026 to 3 October 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.
河北人社 社会保障卡 亲情账户维护 添加 重置社保密码 刷人脸 抓包过不去 https://www.sjz12333.net/ywtb/#/registerOne 打开 个人登录 找回密码 输入二要素 社保卡号需要补齐 社保密码 重置 密码 然后石家庄人社登录 就业创业抓包找https://www.sjz12333.net/ggfw/config/message.json?access_token=23a9e3b0-3c7a-42ac-bb78-8d8266802104这个 然后手动输入py 输入身份证 自动下载社保头带地址 ——@yanyan2107 来自 @qwe_poi_action 搬运自 python_fenx频道 📮 点我投稿
File, posted without a caption
来自 @qwe_poi_action 搬运自 pyjd0频道 📮 点我投稿
📮 新投稿 #33 ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 👤 @readily_accessible 🕐 2026-10-04 00:22 📮 投稿通道 📢 聊天群组
河北股东高管 来自 @qwe_poi_action 搬运自 xiao_i7频道 📮 点我投稿
📮 新投稿 #31 ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 🕶 匿名投稿 🕐 2026-10-03 20:56 https://tysfrz.isdapp.shandong.gov.cn/jpaas-jags-server/interface/gateway.do 山东模糊机主接口会玩的黑壳可以搞一下 📮 投稿通道 📢 聊天群组
👍1
📮 新投稿 #27 ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 👤 @Ne7891 🕐 2026-10-03 20:44 二要.py 📮 投稿通道 📢 聊天群组
👍1
📢投稿机器人上线 机器人：@xiaoniantougao_bot 使用方式： 把内容直接发送给投稿机器人，提交后等待审核。 审核通过后，内容会自动发布到本频道。 如果你的频道添加本机器人并且给了发布权限也会一并发送到你的频道。 欢迎大家积极投稿分享！
📮 新投稿 #23 ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 👤 @aognsooaf 🕐 2026-10-03 18:20 小程序 中荷人寿在线商城 随便打开一个 去投保 输入错误二要素 前面几次显示 身份证存在与名字不匹配 后面几次显示不一致 可以检测身份证是否存在或者非库 响应极快 有本事的可以去弄一下 📮 投稿通道 📢 聊天群组
👍1
📮 新投稿 #16 ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 🕶 匿名投稿 🕐 2026-10-03 17:16 1蒋介石（本名） 2蒋周泰（蒋介石谱名） 3蒋瑞元（蒋介石幼名） 4蒋志清（蒋介石学名） 5小念 （蒋介石网名） 📮 投稿通道 📢 聊天群组
🔥1🥰1
📮 新投稿 #12 ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 👤 @ez7886 🕐 2026-10-03 13:41 红包 该快手账号🆔 频繁发布色情擦边短剧，利用暧昧剧情和暗示性台词诱导观众私信，进而发送收费淫秽视频链接。同时该账号还引导用户进入付费群组，传播大量低俗内容。现提供其作品截图和群聊记录，请求平台快速封禁该账号，冻结其打赏及支付渠道，并移交文化执法部门处理。望平台优先审核此案，及时封禁。 📮 投稿通道 📢 聊天群组
👍1🤩1
📮 新投稿 #13 ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 👤 用户8857284807 🕐 2026-10-03 13:40 微信好友端思路： 给对面发红包任意金额-发几句在不在-提欺诈口收款不发货➕账号被盗-聊天记录选上你发的红包和在不在-举报理由填：对面收款不发货诈骗请封禁该账号 注：拿这个圈钱的傻逼是不是天才又不是百分百的东西有的人还自称百分百 📮 投稿通道 📢 聊天群组
👍3
Showing the 12 most recent of 20 posts we hold for @xiaonianfenxiang. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
@xiaonianfenxiang named 1 handle 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“小念PY公益分享2频” (@xiaonianfenxiang), 1,467 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/xiaonianfenxiang.
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.