美团外卖地址,出6个月内 最近1条记录 8️⃣0️⃣💰 最近3条记录1️⃣0️⃣0️⃣💰 回单:文字编辑地址➕带时间 当天或隔天回 每天限量20个

Channel
24小时源头查档开停通知
@yuantouchad
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
6,057subscribers
+1,790 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1004462699139 |
|---|---|
| Type | Channel |
| Username | @yuantouchad |
| Created | Between 1 June 2026 and 21 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/yuantouchad |
Topic
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 94% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 04:37 | 6,057 | +183 |
| 12 Sept 2026, 05:56 | 5,874 | +264 |
| 8 Sept 2026, 06:55 | 5,610 | +338 |
| 3 Sept 2026, 00:15 | 5,272 | +216 |
| 30 Aug 2026, 20:25 | 5,056 | +310 |
| 27 Aug 2026, 14:04 | 4,746 | +333 |
| 24 Aug 2026, 20:18 | 4,413 | +146 |
| 23 Aug 2026, 19:01 | 4,267 | first reading |
Engagement
20 posts held, back to 21 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 · 30 days
- 2.31%
- avg views ÷ 6,057 subscribers
- Avg views / post
- 140
- 5 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 5
- of 20 held
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 23 August 2026 |
|---|---|
| Posts held | 20 (21 August 2026 – 23 August 2026) |
| Views total | 701 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Aug 2026, 19:01 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.
Recent posts
美饿一体 回单没收到的明天 1️⃣8️⃣0️⃣ 姓名身份证手机号报 回三个月内最新十条收货地址 超过三个月的记录全部回空 系统如果没有十条 一条也收费 敏感收费 不堵车当天隔天回 很稳定
全国正反 8️⃣💰秒 批量来谈
收20单,原图司法 带经办人 明天下午下班回单 今天晚上9点发车 需要的老板来
网逃 开 5️⃣0️⃣💰 今天回 没有事由!
车大档 3️⃣5️⃣💰 今晚回
微信支付宝流水全回 微信流水 不带ID 支付宝流水 带ID 一月 6️⃣0️⃣0️⃣💰 三月 7️⃣0️⃣0️⃣💰 六月 9️⃣0️⃣0️⃣💰 下周回 来个小批量谈价格 要15单 要么全部微信 要么全部支付宝 能包的来
美饿一体 开 1️⃣8️⃣0️⃣ 姓名身份证手机号报 回三个月内最新十条收货地址 超过三个月的记录全部回空 系统如果没有十条 一条也收费 不堵车当天隔天回 很稳定
车轨 5+1 1️⃣6️⃣0️⃣💰 源头直收, 车辆轨迹查询 5+1页 一页内容具体看图 最后的1代表会给你个监控抓拍的照片 近一个月记录,个别会没有车图 保真不包漏,一条也收费 工作日当天,隔天回 ——————————————— 敏感收费不给单
开工
老版开普勒手机轨迹 降价处理 1️⃣5️⃣0️⃣💰 提供手机号 出近一年手机轨迹 数据超5条默认出单 包真不包漏 识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑,所以个别位置会有误导识别现象,产生经纬跳跃 结果以总体较多出现的位置为准。
手机号封禁 2️⃣5️⃣💰 封禁30天后申诉不通过 相当于卡直接报废申诉成功概率极低 结果1 停机打不了电话 接不了电话 发不了短信 用不了流量 结果2冻结 同上 区别是可以接电话 最新报单规则 不接受扯皮 报单不撤 验收以百度标记为准 当天提交 运营商同步百度1-5 天 可以拿自己手机号测试 不接受扯皮
Showing the 12 most recent of 20 posts we hold for @yuantouchad. 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.
Mentions
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.
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.
Cite this entry
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“24小时源头查档开停通知” (@yuantouchad), 6,057 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/yuantouchad.
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.