数据渗透 频道 https://t.me/shentouWebAppIpa 客服 @HexVoid_robot #付费置顶月广轮发 12-5 到期
👍6

Channel
@Py_Jay_geqian
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
8,288subscribers
+1,192 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003965518758 |
|---|---|
| Type | Channel |
| Username | @Py_Jay_geqian |
| Description | 分享各种py文件/工具/思路 让你拥有一个安心可靠的技术交流学习通道 联系/投稿/供需 - @jay_geqianbot 技术交流基地 - @Jay_jsjl 防失联 - @Gqfsl 本频道为技术分享频道 ,频道中投稿分享的所有漏洞请涉事官方尽快修复!避免不法分子滥用造成危害 漏洞信息披露、安全预警、技术研究、漏洞分析、风险通报 |
| Created | Between 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/Py_Jay_geqian |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 12 Nov 2026, 06:08 | 8,288 | -194 |
| 8 Nov 2026, 09:55 | 8,482 | -27 |
| 4 Nov 2026, 23:50 | 8,509 | -18 |
| 1 Nov 2026, 15:39 | 8,527 | +435 |
| 29 Oct 2026, 22:48 | 8,092 | -88 |
| 27 Oct 2026, 06:27 | 8,180 | -18 |
| 23 Oct 2026, 23:19 | 8,198 | +237 |
| 21 Oct 2026, 07:16 | 7,961 | -181 |
| 17 Oct 2026, 22:06 | 8,142 | +817 |
| 15 Oct 2026, 01:36 | 7,325 | -200 |
| 11 Oct 2026, 12:21 | 7,525 | -2 |
| 5 Oct 2026, 09:17 | 7,527 | +34 |
| 26 Sept 2026, 19:55 | 7,493 | +118 |
| 18 Sept 2026, 00:21 | 7,375 | -35 |
| 13 Sept 2026, 14:01 | 7,410 | +96 |
| 9 Sept 2026, 22:41 | 7,314 | +100 |
| 4 Sept 2026, 05:01 | 7,214 | -20 |
| 31 Aug 2026, 17:04 | 7,234 | -5 |
| 28 Aug 2026, 14:23 | 7,239 | +23 |
| 25 Aug 2026, 13:29 | 7,216 | first reading |
152 posts held, back to 6 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 38 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. It is computed over the 79 of 83 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 152 (6 August 2026 – 13 November 2026) |
| Views total | 68,142 |
| Reactions total | 1,187 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 02:09 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 November 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.
Measured directly from 10 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.
1,917 reactions across 145 posts, in 20 distinct kinds. The most used accounts for 44.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 853 | 44.5% | |
| 🤣 | 420 | 21.9% | |
| 🤔 | 219 | 11.4% | |
| 👎 | 159 | 8.29% | |
| 😱 | 53 | 2.76% | |
| 🌭 | 50 | 2.61% | |
| 🤡 | 38 | 1.98% | |
| 🍌 | 31 | 1.62% | |
| 😁 | 21 | 1.10% | |
| 🕊 | 13 | 0.678% | |
| 👏 | 12 | 0.626% | |
| 😭 | 8 | 0.417% | |
| 🤩 | 7 | 0.365% | |
| 😡 | 6 | 0.313% | |
| 😢 | 6 | 0.313% | |
| 🤓 | 6 | 0.313% | |
| 🥰 | 5 | 0.261% | |
| 👌 | 4 | 0.209% | |
| 🤯 | 4 | 0.209% | |
| 😨 | 2 | 0.104% |
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 145 of the 152 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 1,917 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 152 most recent posts we hold, published 6 August 2026 to 13 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: 2 of 83 posts held from the last 30 days (2.41%) 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).
数据渗透 频道 https://t.me/shentouWebAppIpa 客服 @HexVoid_robot #付费置顶月广轮发 12-5 到期
👍6
高价收江苏法人9192无遗漏接口,可出法人证件号+手机号(全号) 联系:@Dusheschips 高价收江苏法人9192无遗漏接口,可出法人证件号+手机号(全号) 联系:@Dusheschips #付费置顶周广轮发 11-20到期
👍5🤔2
#小程序://安顾e家/dsErBOuRwj5Wfjt 运营商手机名字验证 ——律师 📮 投稿通道 ☘️ 交流群组
👍10🤔5
#小程序:开江县妇幼保健计划生育服务中心 无限制二要素 ---匿名投稿 📮 投稿通道 ☘️ 交流群组
👍6🤔3🤣3👎2
出过的出不了 注意手机号不能瞎填 后面打开证照要接码 ——py基地 📮 投稿通道 ☘️ 交流群组
🤣7🍌2👍2🌭1
#湖南学籍 #湖南监护人 ——i分享 📮 投稿通道 ☘️ 交流群组
👍7👎3🤔2
天猫APP→号密码登录→忘记密码→输入手机号(/用户名/邮箱)→手机号已停用→联系官方客服→图一所示修改手机→再次输入已输入的查询信息→(出现绑定用户名称)→拍摄脸部+账号密码验证→开始认证→如图二所示出现实名... 投稿人--@XNnb666666666 📮 投稿通道 ☘️ 交流群组
👍11🤔3👎2
原作者:@List521 只不过他做的手机无法使用,我重制了而已 @love_xuwei @zzzxwxn @l71368 这三个诈骗犯严禁使用 使用了自动死全家 投稿人--@BMDCDA 📮 投稿通道 ☘️ 交流群组
🤣10👍6🤔1
漏洞描述: 支付宝小程序 “亲密号” 功能对应帮孩子注册支付宝(需要未成年账号)hook抓包可以查询名下uid,无鉴权成年人也可被批量调用,用于批量核验支付宝实名信息和查询名下支付宝账号。 风险等级:高危,支付宝内部口子,需要一台手机一直开着或者买虚拟机挂着可hook调取口子 ---匿名投稿 📮 投稿通道 ☘️ 交流群组
👍8🤔3🤣2👌1
市面上的名下支付宝 和uid支3 以及调用办法 市场龙头只有一个 是谁不用多说 拿着别人告诉你的口子装逼 搞笑 奇异搞笑 自己挖不出来 你看这个口子死了你爹还有没有别的 支名挖出来了吗弟弟 ps:上面的发错了 发成之前的蚂蚁保了 这个才是 把这个改成批量就是uid支3了 ——i分享 📮 投稿通道 ☘️ 交流群组
👍8🤣6🤔3
gov口卡4 自己写批量 无限制 -效果展示- ——i分享 📮 投稿通道 ☘️ 交流群组
👍8🤔6👎2
小程序://信易贷/tJGPPV2CnvcsNtk ——i分享 📮 投稿通道 ☘️ 交流群组
👍8👎6
Showing the 12 most recent of 152 posts we hold for @Py_Jay_geqian. 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 22 posts on @Py_Jay_geqian 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.
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.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“Py分享基地【编程/技术/分享】” (@Py_Jay_geqian), 8,288 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/Py_Jay_geqian.
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.