📣i分享供需广告咨询来了! 供需怎么发来着 发布者 @nian73694 思路分享 交流群组 思路投稿 供需频道
👍5🤣2😱1

Channel
@Python_shijie
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
41,613subscribers
+16,536 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002437919487 |
|---|---|
| Type | Channel |
| Username | @Python_shijie |
| Description | 此频道为历史遗迹频道,作废不再更新!以后作为付费供需频道 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/Python_shijie |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 17:28 | 41,613 | -29 |
| 13 Oct 2026, 07:47 | 41,642 | -93 |
| 9 Oct 2026, 02:57 | 41,735 | -92 |
| 4 Oct 2026, 14:17 | 41,827 | +7,566 |
| 26 Sept 2026, 09:55 | 34,261 | -89 |
| 19 Sept 2026, 14:37 | 34,350 | -1,263 |
| 17 Sept 2026, 04:20 | 35,613 | -10 |
| 15 Sept 2026, 08:16 | 35,623 | -3 |
| 13 Sept 2026, 16:01 | 35,626 | +33 |
| 11 Sept 2026, 19:22 | 35,593 | +2 |
| 9 Sept 2026, 07:01 | 35,591 | +8 |
| 5 Sept 2026, 21:21 | 35,583 | -6 |
| 3 Sept 2026, 16:58 | 35,589 | -6 |
| 2 Sept 2026, 07:52 | 35,595 | -14 |
| 1 Sept 2026, 04:18 | 35,609 | -11 |
| 31 Aug 2026, 03:27 | 35,620 | -9 |
| 30 Aug 2026, 00:05 | 35,629 | -2 |
| 29 Aug 2026, 02:16 | 35,631 | -12 |
| 28 Aug 2026, 00:04 | 35,643 | +7 |
| 26 Aug 2026, 00:27 | 35,636 | first reading |
180 posts held, back to 3 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 114 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 14 October 2026 |
|---|---|
| Posts held | 180 (3 August 2026 – 14 October 2026) |
| Views total | 244,714 |
| Reactions total | 804 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Oct 2026, 21:07 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 14 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
979 reactions across 180 posts, in 11 distinct kinds. The most used accounts for 53.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 520 | 53.1% | |
| ❤ | 198 | 20.2% | |
| 🤣 | 85 | 8.68% | |
| 🔥 | 61 | 6.23% | |
| 👏 | 45 | 4.60% | |
| 🤡 | 36 | 3.68% | |
| 👎 | 19 | 1.94% | |
| 😱 | 5 | 0.511% | |
| 🤩 | 5 | 0.511% | |
| 😭 | 3 | 0.306% | |
| 🤔 | 2 | 0.204% |
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 180 of the 180 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 979 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 180 most recent posts we hold, published 3 August 2026 to 14 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Python_shijie. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 180 most recent posts we hold for this entry, published 3 August 2026 to 14 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
📣i分享供需广告咨询来了! 供需怎么发来着 发布者 @nian73694 思路分享 交流群组 思路投稿 供需频道
👍5🤣2😱1
📣i分享供需广告咨询来了! 供应商品:身份证号性别二要素核验 商品介绍:全国身份证号性别核验,不抽风不遗漏一秒一万个质保十年 商品价格:100000u 是否售后:支持 是否支持担保:天地银行担保 保费哪方承担:玉皇大帝 交易货币支持:冥币 发布者 @nian73694 思路分享 交流群组 思路投稿 供需频道
🤣4👍3
📣i分享供需广告咨询来了! ❌ 请包含文字内容 供需消息必须有文字描述。 发布者 @nian73694 思路分享 交流群组 思路投稿 供需频道
👍3🤣2
📣i分享供需广告咨询来了! TG最强公益封号思路频道❗️ TG最强公益封号思路频道❗️ TG最强公益封号思路频道❗️ 本频道公益任何封号思路⚠️ 快手、微信、小红书、抖音、QQ、TG 唯一频道链接打压任何公益频道👆 https://t.me/XNfen https://t.me/XNfen https://t.me/XNfen 本频道公益任何封号思路教程教学💬 频道活跃人数非常高🔥 广告咨询: @huanjue_ttkx 24小时号铺链接🔗 售卖快手抖音微信低价2块TG号 https://vip.ymy9.com/shop/huanjue 点击即可购买任意接码账号👍 加入我们的频道✅ @XNfen @xueluoqingyan 发布者 @huanjue_ttkx 思路分享 交流群组 思路投稿 供需频道
👍5
📣i分享供需广告咨询来了! 我说白了,都先别说话,有没有发我点精品片,没片看了 发布者 @pamiyl 思路分享 交流群组 思路投稿 供需频道
👍9
📣i分享供需广告咨询来了! 每晚200左右二要素出电话,要求支付宝或运营商三要素验证一致的,大概500u一个月相当于5毛一条 能做的速度 发布者 @kky_by 思路分享 交流群组 思路投稿 供需频道
👍3👎2
📣i分享供需广告咨询来了! 🌟异曲同工核验助手 免费核验机器人。支持身份证二要素核验、运营商三要素,手机二要素核验,法人四要素核验,,京东模糊,银行卡三、四要素核验,,银行卡开户行查询,婚姻状态查询 ,营业执照生成 ,更多功能等你体验...... ✅异曲同工公益查询群组 :https://t.me/BTMRaaaa 支持查询京东美团模糊位 全国常用号 ✅异曲同工官方频道 https://t.me/soqbDj ✅异曲同工核验助手 @yqtg113_Bot ✅免费假地BOT :@yqtgjgbot 发布者 @love_shengong 思路分享 交流群组 思路投稿 供需频道
❤3
📣i分享供需广告咨询来了! 少妇u老牌查档机构 只做源头业务 源头人脸点射40U 源头人脸点射40U 源头人脸点射40U 不过核验不收钱 不准不算单 已打假市面五头版本 还有一些出不来单的同行 源头破解微反20U 源头破解微反20U 源头破解微反20U 有名没名都可以试试 不托单 效率高 源头移动百分百35U 源头移动百分百35U 源头移动百分百35U 人在秒 真正的百分百出单率 什么烂货都可以拿的下 以上业务 有量代理 同行 拿价格 以上业务 有量代理 同行 拿价格 以上业务 有量代理 同行 拿价格 卫健五年医疗25U 犯罪记录35U 大数据征信35U 邮政单地址4U 多地址12U 烂货机主支机15U 更好用的自助业务机器人 @shaofuuzh_bot 对接人 @shaofuu 发布者 @shaofuu 思路分享 交流群组 思路投稿 供需频道
👍3🤣2
📣i分享供需广告咨询来了! 为什么拿得起 缺放不下 @zhi_jianbot @zhi_jianbot @zhi_jianbot 知简 · 让复杂的事情 简单一点 通用VIP卡密 VIP-A66EA0638EFC 发布者 匿名 思路分享 交流群组 思路投稿 供需频道
🤡4😭1
📣i分享供需广告咨询来了! 群发机器人6.6U一个月,机器人独享不与他人共用,可以设置文字状态和会员表情包,春江打广告你是最靓的仔,需要的私信: @hui520ovo 发布者 @hui520ovo 思路分享 交流群组 思路投稿 供需频道
👍6
📣i分享供需广告咨询来了! 😃😃😃😃 (32)🤖江苏神父🤖😀😀秒 (45)🤖广西神父🤖😀😀秒 (46)🤖海南神父🤖😀😀秒 (43)🤖湖南神父🤖😀😀秒 (12)🤖天津神父🤖😀😀秒 (65)🤖新疆神父🤖😀😀 (42)🤖湖北神父🤖😃😀秒 (52)🤖贵州神父🤖😀😀秒 (36)🤖江西神父🤖😀😀秒 (37)🤖山东神父🤖😀😀秒 (62)🤖甘肃神父🤖😀😀秒 (41)🤖河南神父🤖😀😀秒 (33)🤖浙江神父🤖😃😀 (34)🤖安徽神父🤖😃😀 报单联系 @pingfanxin 公网户籍地系列: 11北京、34安徽、37山东、43湖南、44广东、50重庆、62甘肃 😃 白天附带大头一起出 发布者 @leisai777 思路分享 交流群组 思路投稿 供需频道
👍6🔥1🤔1
📣i分享供需广告咨询来了! 【sore一站式查档 源头优势欢迎前来合作】 户籍/身份证/社保/学历/医疗/婚姻/护照/车辆/法人/找人 反查项目 微信/抖音/支付宝/小红书/银行卡/手机号/护照 定位轨迹:开房/外卖/快递/出入境/手机定位/车辆轨迹 案件查询:网逃/案件详情/立案/涉案/判决书/司法冻结 对接人: @soredly 点击字体进入公群 已押13140U 订阅频道关注最新优势业务 点击进入 订阅频道查看业务模板列表 点击进入 关注通知频道 及时获取最新业务通知价格及优势 以避免不必要的信息差 感谢配合 sore|专业沟通|高效处理|全天在线 发布者 @Soredly 思路分享 交流群组 思路投稿 供需频道
👍3🔥1
Showing the 12 most recent of 180 posts we hold for @Python_shijie. 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.
Named by 3 registered channels — 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.
@Python_shijie named 9 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“i分享『供需频道』” (@Python_shijie), 41,613 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/Python_shijie.
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.