飞机群发 拉人 私信 炒群 代发广告 飞机号批发 可以测试 数据业务 苹果超级签 app谷歌上架 安卓处报毒 美国号api 业务 支持 电报 qq 微博 抖音 快手 领英 陌陌 今日头条 小红书 爱奇艺 无忧行 土豆 滴滴 优步 西瓜 支付宝 网易 等各种冷门业务 软件视频频道 @zh_cn188 飞机号频道 @hao1238cc 常用飞机 @xzskefu01 @feijihao0 qq 443380497 2835293963
👍13😁7🔥5👏3🥰1

Channel
@hao1238cc
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6,485subscribers
-10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001795781106 |
|---|---|
| Type | Channel |
| Username | @hao1238cc |
| Created | 14 March 2022 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/hao1238cc |
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 60% 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 |
|---|---|---|
| 13 Oct 2026, 05:37 | 6,485 | -3 |
| 30 Sept 2026, 17:58 | 6,488 | -5 |
| 12 Sept 2026, 18:40 | 6,493 | -1 |
| 8 Sept 2026, 18:57 | 6,494 | -1 |
| 3 Sept 2026, 20:41 | 6,495 | -2 |
| 16 Aug 2026, 08:05 | 6,497 | +1 |
| 12 Aug 2026, 13:23 | 6,496 | +1 |
| 6 Aug 2026, 22:15 | 6,495 | no change |
| 6 Aug 2026, 22:08 | 6,495 | first reading |
12 posts held, back to 14 March 2022 — 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 12 posts for this entry, the most recent from 10 April 2022. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
52 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 63.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 33 | 63.5% | |
| 😁 | 9 | 17.3% | |
| 🔥 | 5 | 9.62% | |
| 👏 | 3 | 5.77% | |
| ❤ | 1 | 1.92% | |
| 🥰 | 1 | 1.92% |
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 6 of the 12 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 52 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 14 March 2022 to 10 April 2022, 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谷歌上架 安卓处报毒 美国号api 业务 支持 电报 qq 微博 抖音 快手 领英 陌陌 今日头条 小红书 爱奇艺 无忧行 土豆 滴滴 优步 西瓜 支付宝 网易 等各种冷门业务 软件视频频道 @zh_cn188 飞机号频道 @hao1238cc 常用飞机 @xzskefu01 @feijihao0 qq 443380497 2835293963
👍13😁7🔥5👏3🥰1
飞机号 美国号api pinned «飞机群发 拉人 私信 炒群 代发广告 飞机号批发 可以测试 还有数据业务 美国号api 业务 支持 电报 qq 微博 抖音 快手 领英 陌陌 今日头条 小红书 爱奇艺 无忧行 土豆 滴滴 优步 西瓜 支付宝 网易 等各种冷门业务 飞机中文导航群 @hao166 软件视频频道 @zh_cn188 飞机号频道 @hao1238cc 常用飞机 @xzskefu01 @feijihao0 qq 443380497 2835293963»
飞机群发 拉人 私信 炒群 代发广告 飞机号批发 可以测试 还有数据业务 美国号api 业务 支持 电报 qq 微博 抖音 快手 领英 陌陌 今日头条 小红书 爱奇艺 无忧行 土豆 滴滴 优步 西瓜 支付宝 网易 等各种冷门业务 飞机中文导航群 @hao166 软件视频频道 @zh_cn188 飞机号频道 @hao1238cc 常用飞机 @xzskefu01 @feijihao0 qq 443380497 2835293963
👍11😁2❤1
104 47 端口飞机号现货
飞机号 美国号api pinned «大量出美国API、全新接口,新接口服务器,全新首次、WeChat、企业WeChat、得物、京东、知乎、抖音、头条、西瓜、tiktok、腾讯视频、QQ、快手、微博、美团、脸书、华为、tb、蝙蝠、懂车帝、比心、Telegram、line 、blued、whatsapp、nike、BitClout、悟空、网易、FIGO 、soul、uber、积目、斗鱼、虎牙、滴滴、陌陌、探探、爱奇艺视频、亚马逊、UU加速器、小红书、大众点评、人人视频、红蓝CP、恋爱物语、捞月狗、天龙八部、领英 各种冷门都有货»
大量出美国API、全新接口,新接口服务器,全新首次、WeChat、企业WeChat、得物、京东、知乎、抖音、头条、西瓜、tiktok、腾讯视频、QQ、快手、微博、美团、脸书、华为、tb、蝙蝠、懂车帝、比心、Telegram、line 、blued、whatsapp、nike、BitClout、悟空、网易、FIGO 、soul、uber、积目、斗鱼、虎牙、滴滴、陌陌、探探、爱奇艺视频、亚马逊、UU加速器、小红书、大众点评、人人视频、红蓝CP、恋爱物语、捞月狗、天龙八部、领英 各种冷门都有货
👍4
47端口美国号
👍4
104端口美国号
👍1
Channel photo updated
飞机号 美国号api pinned «飞机号成品号 协议号 美国api号批发 零售 各行业优质数据 股票 网贷 pos 信用卡 银行 棋牌 六合彩, 飞机群发 拉人 私信 炒群 代发广告 所有业务均可测试 主号 @xzskefu01 q 443380497 2835293963»
飞机号成品号 协议号 美国api号批发 零售 各行业优质数据 股票 网贷 pos 信用卡 银行 棋牌 六合彩, 飞机群发 拉人 私信 炒群 代发广告 所有业务均可测试 主号 @xzskefu01 q 443380497 2835293963
Channel created
Showing the 12 most recent of 12 posts we hold for @hao1238cc. 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.
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.
@hao1238cc named 1 handle 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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“飞机号 美国号api” (@hao1238cc), 6,485 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/hao1238cc.
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.