全国社保常用号思路 《教程》: 应用商店下载app:电子社保卡 去登录界面-点忘记密码-输入姓名和身份证号 点击下一步。 然后就能概率出模糊手机号,含前3和后4位。 最后拿去补齐即可! #接口或思路 “来自 @qwe_poi_action 投稿人 @ai_fh 📮 点我投稿”
Signed 墨白 @Moarketbot

Channel
@MXLGS
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
95,511subscribers
-2,251 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1003800313841 |
|---|---|
| Type | Channel |
| Username | @MXLGS |
| Description | MX编程灵感社|专注Python基础学习思路交流,仅限公开解题技巧研讨。For study only,strictly comply with Telegram's Terms of Service,violating content wi |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/MXLGS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 16:56 | 95,511 | -64 |
| 28 Aug 2026, 13:22 | 95,575 | -8 |
| 27 Aug 2026, 16:13 | 95,583 | -32 |
| 26 Aug 2026, 13:25 | 95,615 | -61 |
| 25 Aug 2026, 16:28 | 95,676 | -119 |
| 24 Aug 2026, 15:55 | 95,795 | -191 |
| 23 Aug 2026, 03:18 | 95,986 | -182 |
| 21 Aug 2026, 13:06 | 96,168 | -62 |
| 20 Aug 2026, 15:34 | 96,230 | -143 |
| 19 Aug 2026, 16:18 | 96,373 | -192 |
| 18 Aug 2026, 18:16 | 96,565 | -213 |
| 17 Aug 2026, 16:04 | 96,778 | -252 |
| 16 Aug 2026, 07:56 | 97,030 | -258 |
| 14 Aug 2026, 19:07 | 97,288 | -254 |
| 13 Aug 2026, 07:53 | 97,542 | -211 |
| 12 Aug 2026, 07:42 | 97,753 | -9 |
| 12 Aug 2026, 03:30 | 97,762 | no change |
| 12 Aug 2026, 03:17 | 97,762 | first reading |
131 posts held, back to 9 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 42 pagesof 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 91 of 131 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 131 (9 August 2026 – 30 August 2026) |
| Views total | 173,496 |
| Reactions total | 1,640 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 03:59 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 30 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.
Measured directly from 5 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,640 reactions across 87 posts, in 16 distinct kinds. The most used accounts for 19.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 323 | 19.7% | |
| 🤮 | 318 | 19.4% | |
| 👎 | 310 | 18.9% | |
| 😱 | 278 | 17.0% | |
| 😢 | 272 | 16.6% | |
| ❤ | 58 | 3.54% | |
| 👍 | 58 | 3.54% | |
| 🤣 | 11 | 0.671% | |
| 👏 | 2 | 0.122% | |
| 🔥 | 2 | 0.122% | |
| 🖕 | 2 | 0.122% | |
| 😁 | 2 | 0.122% | |
| 😍 | 1 | 0.061% | |
| 🤡 | 1 | 0.061% | |
| 🤩 | 1 | 0.061% | |
| 🤪 | 1 | 0.061% |
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 91 of the 131 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,640reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 131 most recent posts we hold, published 9 August 2026 to 30 August 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.
全国社保常用号思路 《教程》: 应用商店下载app:电子社保卡 去登录界面-点忘记密码-输入姓名和身份证号 点击下一步。 然后就能概率出模糊手机号,含前3和后4位。 最后拿去补齐即可! #接口或思路 “来自 @qwe_poi_action 投稿人 @ai_fh 📮 点我投稿”
Signed 墨白 @Moarketbot
❤️查档圈新闻❤️ t.me/cdqxw t.me/cdqxw t.me/cdqxw 曝光社工库跑路,公群老板黑料,数据真假,查档漏洞,市场经济,犯罪人员等等,还有各种趣事。
Signed 🤖群管 group
在线收全新未泛滥全国92工商个体户接口,单个省份也收, 要求: 1.要能批量无限制 2.能出每天最新更新的个体数据 2.要有准确法人预留电话号码,身份证号码可有可无 4.有云南,安徽,河南,广西,的优先 联系 @Mysql5 #单月轮发广告@MXLGS 2026.9.6到期
Signed 🤖群管 group
全网最牛逼的综合机器人 鼎盛综合机器人 @DnshZhBOT 双网名下号0.5U 联通电信无遗漏 正反/盖章/真地址个户 6.6 U 大头+户籍地+民族 保真保最新 大头照/假地址 1U 以下24小时秒出↓ 免费加工正反盖章 可过法院诉讼 出入境带名下护照 2.5U 婚姻记录 3U 联通机主 5U 地区个户 1U 支付宝秒出姓名 0.5U 名下公司 1U 人脸对比 0.1U 机主二三要素 0.1U 银行卡二三四要素 0.1U 法人四要素 0.1U 姓名身份证二要素 0.1U 携号转网 0.1U 免费法人前六后四 免费银行卡详情 免费手机号归属地 免费15位身份证号转18位 机器人: @DnshZhBOT
Signed 🤖群管 group
这个新加坡真不错
👍3
Signed 墨白 @Moarketbot
高速韩国代理 高速香港代理 高速美国代理 dc4专用意大利代理 推荐高速新加坡节点2000mbps 自己搭的代理 速度还行 起码能看片
👎5👍3💩1🤡1
Signed 墨白 @Moarketbot
❤️查档圈新闻❤️ t.me/cdqxw t.me/cdqxw t.me/cdqxw 曝光社工库跑路,公群老板黑料,数据真假,查档漏洞,市场经济,犯罪人员等等,还有各种趣事。
Signed 🤖群管 group
在线收全新未泛滥全国92工商个体户接口,单个省份也收, 要求: 1.要能批量无限制 2.能出每天最新更新的个体数据 2.要有准确法人预留电话号码,身份证号码可有可无 4.有云南,安徽,河南,广西,的优先 联系 @Mysql5 #单月轮发广告@MXLGS 2026.9.6到期
Signed 🤖群管 group
全网最牛逼的综合机器人 鼎盛综合机器人 @DnshZhBOT 双网名下号0.5U 联通电信无遗漏 正反/盖章/真地址个户 6.6 U 大头+户籍地+民族 保真保最新 大头照/假地址 1U 以下24小时秒出↓ 免费加工正反盖章 可过法院诉讼 出入境带名下护照 2.5U 婚姻记录 3U 联通机主 5U 地区个户 1U 支付宝秒出姓名 0.5U 名下公司 1U 人脸对比 0.1U 机主二三要素 0.1U 银行卡二三四要素 0.1U 法人四要素 0.1U 姓名身份证二要素 0.1U 携号转网 0.1U 免费法人前六后四 免费银行卡详情 免费手机号归属地 免费15位身份证号转18位 机器人: @DnshZhBOT
Signed 🤖群管 group
单次支付宝三要素 应用商店花生返利app 提现口 ---- @cqbjn ✨ 投稿通道 📢 频道 💬 交流群 ⚠️ 免责声明: 🔒 【Compliance & Usage Statement】 This Python file is provided solely for technical learning and open-source communication purposes. It contains no malicious code, non-compliant modules, or functions that violate Telegram's Terms of Service. The file is open-source and verifiable, intended only for authorized legal scenarios. Any unauthorized or ill…
👍2🤣2🔥1
Signed MX投稿机器人
乱世用ai开源不出来 我自己开源了 ----热心网友 ✨ 投稿通道 📢 频道 💬 交流群 ⚠️ 免责声明: 🔒 【Compliance & Usage Statement】 This Python file is provided solely for technical learning and open-source communication purposes. It contains no malicious code, non-compliant modules, or functions that violate Telegram's Terms of Service. The file is open-source and verifiable, intended only for authorized legal scenarios. Any unauthorized or illegal use i…
❤2👍1🤣1🤩1
Signed MX投稿机器人
#小程序://嘟嘟管家/gkEd4LRukpn2hpe 登录自己获取小程序手机号的验证码 输入验证码可以批量三要素核验几百条左右 验证码一样也是无限制 自己替换tk即可 ---- @fangqinb ✨ 投稿通道 📢 频道 💬 交流群 ⚠️ 免责声明: 🔒 【Compliance & Usage Statement】 This Python file is provided solely for technical learning and open-source communication purposes. It contains no malicious code, non-compliant modules, or functions that violate Telegram's Terms of Service. The file is open-source and verifiable, intend…
❤1👍1
Signed MX投稿机器人
Showing the 12 most recent of 131 posts we hold for @MXLGS. 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.
Citation-graph rank — 1,508,910 of 1,626,884entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
@MXLGS named 2 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“MX灵感社┣ py ┫技术分享 -查档-开盒_思路_免费开户__大杂烩” (@MXLGS), 95,511 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/MXLGS.
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.