Channel
@doufan
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
12,885subscribers
+11,030 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003903752177 |
|---|---|
| Type | Channel |
| Username | @doufan |
| Created | 5 August 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/doufan |
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 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 |
|---|---|---|
| 25 Sept 2026, 13:22 | 12,885 | +405 |
| 19 Sept 2026, 00:16 | 12,480 | +256 |
| 16 Sept 2026, 18:15 | 12,224 | +223 |
| 15 Sept 2026, 00:18 | 12,001 | +205 |
| 13 Sept 2026, 07:58 | 11,796 | +235 |
| 11 Sept 2026, 11:57 | 11,561 | -503 |
| 8 Sept 2026, 20:56 | 12,064 | +151 |
| 5 Sept 2026, 10:22 | 11,913 | +2,329 |
| 1 Sept 2026, 08:45 | 9,584 | +563 |
| 28 Aug 2026, 22:46 | 9,021 | +261 |
| 26 Aug 2026, 05:42 | 8,760 | +393 |
| 22 Aug 2026, 22:35 | 8,367 | +2,268 |
| 19 Aug 2026, 02:23 | 6,099 | +224 |
| 16 Aug 2026, 02:14 | 5,875 | +87 |
| 12 Aug 2026, 03:12 | 5,788 | +3,861 |
| 8 Aug 2026, 19:43 | 1,927 | +72 |
| 8 Aug 2026, 07:50 | 1,855 | no change |
| 8 Aug 2026, 07:49 | 1,855 | first reading |
32 posts held, back to 5 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 9 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 32 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
公网手机号反小红书：最近系统恢复了稳定隔天回单！出单率依旧高！每晚10点发车，请各用户卡好时间哦~ 公网手机号反社交账号：这边目前出单率是95％，有一些回空的是历史和无用的隐私号，回单前我们都会做批量筛选，除实时数据能过验证以外的都不会回单（避免扯皮）您可以找客服备注说明要历史绑或隐私号 可以先报外面的低价破解，没出的报我这，不过可能会浪费一天时间，我这出单率是比外面通讯录破解都要高的，价格摆在这里，一分价钱一分货。 各位老板们 还是那句话：这个市场比的不是谁价格更低，而是谁货更硬！
快手/小红书 已开！ 请在机器人中报单 @douyinyewubot 价格还是 ⚡.⚡🏆 24小时客服已上线 @FxKf88
名下号做优化处理一下发车问题，那边发车一直飘忽不定的。 明天开始固定北京时间19点30分发车，隔天下午回单。昨天的单子没回给大家带来不便，请谅解。
手机号反社交账号放心报！外面破解空的也可以报，吃一切剩菜，这个市场比的不是谁价格更低，而是谁货更硬！
想在人民币充值P图骗分？两层核查你躲得过去吗，我在飞机5年了，什么高等骗术没见过，像用这种低级手法来骗分的都排不上号，你不如去搞搞拟哈希链，搞冒充高仿虚拟币，还可能有希望 没点技术还想骗分，也就骗骗刚上飞机的小白钱了，晚上还没到呢就想着做梦了？
为响应各位用户人民币 ⚡🏆 充值需求！机器人本次更新已上架 “🧧支付宝口令红包” 支付渠道 本渠道支持 ⚡🏆 充值！ 二维码渠道还在进行处理，新码到了也可以进行 ⚡🏆 充值。 还有什么地方做的不到位的可以来找客服反馈！！您的宝贵反馈是我们优化服务的动力！
快手/小红书，这批回完再发最后一批关了，太催了，本来想着4块钱做公益一单就赚几毛钱利润给大伙发发福利，让大伙能多利用这个，报公网前碰碰运气赚点钱，明确说了能等的报，一堆人催，刚下单几分钟就开始催，一批发下来利润赚不到20块钱，我每天还有其他的事做。实在没空处理，抱歉了 截止今晚23点30分发最后一车彻底关闭报单通道，等后面有空或找到助理再开吧。重新开了会通知。
❗️❗️❗️❗️ 新增：名下号！限时特价（0.3U） 特价持续两天8月26日恢复！ 向机器人发送 /start 刷新业务列表 @douyinyewubot
呼声很高，晚上左右则会添加此功能，这几天太忙了，感谢大家支持！添加后会先特价一天！
Posted without readable text
维护 人民币又需要最低 ⚡🏆了 恢复了会通知 很快 搞到新码就可以了
🔔 [实时播报/每天更新] ✍️ 上一轮小红书/快手反手机号已全部回单进入新一次播报 🔴 小红书快手发车：12/100 两个项目每 😀😃😃 单一车 可以等的就报过来 10出5 概率低，⚡ 块钱的东西 也不吃亏 没发车前可以随时发送 /chedan 撤单 发车会通知这条消息我会每隔几个小时编辑一次，不用来问我什么时候发车看这边数量就可以。
Showing the 12 most recent of 32 posts we hold for @doufan. 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.
@doufan edited 4 posts 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 6 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“奉先通知频道 @doufan” (@doufan), 12,885 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/doufan.
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.