速报: 震惊~ 震惊~ 查档圈首个海外数据社工库,海外电销的朋友有福了,也可以开海外人士了,有多个国家各种软件的。 合作找他 @guanji 详细介绍👉 点击查看 这是机器人 @guanji_sgk_bot
👍7

Channel
@ESU5200
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
12,376subscribers
+450 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003865131386 |
|---|---|
| Type | Channel |
| Usernames | @cdqxw @ESU5200 |
| Created | Between 1 February 2026 and 27 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/ESU5200 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 26 Sept 2026, 21:55 | 12,376 | no change |
| 26 Sept 2026, 21:39 | 12,376 | -13 |
| 19 Sept 2026, 16:42 | 12,389 | -7 |
| 17 Sept 2026, 11:37 | 12,396 | -1 |
| 17 Sept 2026, 04:38 | 12,397 | +9 |
| 15 Sept 2026, 09:56 | 12,388 | -3 |
| 15 Sept 2026, 04:58 | 12,391 | -139 |
| 13 Sept 2026, 16:58 | 12,530 | -1 |
| 13 Sept 2026, 15:38 | 12,531 | -117 |
| 11 Sept 2026, 21:15 | 12,648 | -1 |
| 11 Sept 2026, 19:16 | 12,649 | +38 |
| 9 Sept 2026, 13:38 | 12,611 | +6 |
| 9 Sept 2026, 04:59 | 12,605 | +74 |
| 6 Sept 2026, 07:01 | 12,531 | +14 |
| 5 Sept 2026, 22:40 | 12,517 | +63 |
| 3 Sept 2026, 21:57 | 12,454 | +3 |
| 3 Sept 2026, 16:38 | 12,451 | +52 |
| 2 Sept 2026, 12:34 | 12,399 | -2 |
| 2 Sept 2026, 11:57 | 12,401 | +37 |
| 1 Sept 2026, 13:28 | 12,364 | first reading |
85 posts held, back to 27 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 47 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 32 of 33 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 85 (27 July 2026 – 2 September 2026) |
| Views total | 24,569 |
| Reactions total | 209 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 22:04 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 3 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,419 reactions across 69 posts, in 12 distinct kinds. The most used accounts for 31.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 441 | 31.1% | |
| ❤ | 318 | 22.4% | |
| 👏 | 257 | 18.1% | |
| 🥰 | 251 | 17.7% | |
| 🤡 | 85 | 5.99% | |
| 😱 | 34 | 2.40% | |
| 😭 | 10 | 0.705% | |
| 🗿 | 8 | 0.564% | |
| 😘 | 7 | 0.493% | |
| 🤓 | 5 | 0.352% | |
| 😇 | 2 | 0.141% | |
| 😍 | 1 | 0.07% |
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 72 of the 85 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,419 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 85 most recent posts we hold, published 27 July 2026 to 2 September 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 @ESU5200. 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 85 most recent posts we hold for this entry, published 27 July 2026 to 2 September 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.
速报: 震惊~ 震惊~ 查档圈首个海外数据社工库,海外电销的朋友有福了,也可以开海外人士了,有多个国家各种软件的。 合作找他 @guanji 详细介绍👉 点击查看 这是机器人 @guanji_sgk_bot
👍7
慢报: 阿祖担保跑路了还是被摁了,负责人好多天没有上线了。 查档圈必看👉 A1置顶 唯一商家👉 A2置顶
❤1
明天我弄个以前故事会的那种好玩的吧,弄个侦探小游戏
👍3
好烦啊
👍5
群友投稿: @silaomu 今天交易的时候差点被假担保骗了,骗子拉假欧易担保。 真的👉 @oykf (Y) 假的👉 @oekf (E) 查档圈必看👉 A1置顶 唯一商家👉 A2置顶
👍3❤2
这里是老杨原话
👍3
好人就要被枪指着吗?
🤡5❤2😭2
这件事完整结果 1-水滴筹是真的,诈骗犯是引用那个人的的信息,他可以选任何水滴筹求助信息引用来诈骗,我们捐款到水滴筹的可以退款,也可以不退,因为捐款到水滴筹的确实到了求助人手里。 2-群友们转我的u,和自己转u给他的,计算总共是327.65u,这是他真实诈骗到的u数量。 因为最开始是我发出来这条求助信息的,我承担了,已经全部由我赔偿退完了。
❤5
很多人不要私信骂我 谢谢你们 在sj时刻的频道我投稿我想说一下,小旗不是我 只不过是我的徒弟,我自己刚开始也不清楚 ,白天我看到小熊供需发这个捐款 然后困境私信我 问我能不能发,我就发了,我个人也感受到挺触感的,我自己捐款了50 后来晚上我的换皮号在春江聊天 有人跟我说 这个小旗是骗子 个人收款码,后来我反应过来了,我开始私信骂他,在时刻评论区避雷他 后来小旗跟我说退给我 说是我的徒弟 给了我500左右, 我确实干诈骗 但是今天的东西我自己也不清楚 各位口下留情 别骂我了 ,我在一些广告群发小旗是我徒弟 进群什么的 我也只是想蹭一波流量 OK就这样子 我也想用我自己的力量帮助一些人,很多人说我诈骗,确实我承认我诈骗,但是我诈骗完了,我也不像很多人一样,还要侮辱什么的 我诈骗我敢承认,我也要赚钱,我没有路子,只能诈骗我也每个月都在一些平台上捐款,不信的可以直接私信我看记录, 今天sj时刻被骗我也愧疚 我代替我徒弟跟你们说…
🥰6
u退完了,心累了
❤3
以后我不再收取任何人的钱,你们需要担保的私信担保员四位ID @dduu (记住,一定要先私信确认) 我做回以前那样,好好做我的策划工作,不参与任何交易,并且记住,我不接任何单的。
❤2😱1
查档圈情报-新闻 pinned «本频道由 利兴担保 赞助成立 本频道唯一广告👇 🐙源头微信好友提取带备注 🐙源头微信公众号用户提取 🐙微信支付宝流水反炸版本 🐙微信流水提取带对手ID号 🤭公网微反/QQ收款码反查 😔天花板卡反预留一条龙秒 😎源头十四大柜台流水系列 🫤刑侦无盲三天回银行流水 😭各柜台名下银行卡及带鱼 👮 开同人轨飞火单开大关联 📱 机主法人地址网逃各系列 👮 个人信息 / 个人资产 手机轨迹 通话记录 手机定位 刑侦全户 婚姻记录 学籍学历 名下护照 社保文档 …»
Showing the 12 most recent of 85 posts we hold for @ESU5200. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@ESU5200 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 13 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“查档圈-新闻” (@ESU5200), 12,376 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/ESU5200.
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.