🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源

Channel
武汉出击榜(先锋)
@haoyuane
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
58,888subscribers
+10,089 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001576086238 |
|---|---|
| Type | Channel |
| Username | @haoyuane |
| Description | M |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/haoyuane |
Topic
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 18 Sept 2026, 15:17 | 58,888 | +722 |
| 16 Sept 2026, 05:55 | 58,166 | +208 |
| 14 Sept 2026, 09:38 | 57,958 | +124 |
| 12 Sept 2026, 15:57 | 57,834 | +225 |
| 10 Sept 2026, 12:39 | 57,609 | +762 |
| 7 Sept 2026, 11:57 | 56,847 | +452 |
| 4 Sept 2026, 18:14 | 56,395 | +125 |
| 3 Sept 2026, 00:37 | 56,270 | +122 |
| 1 Sept 2026, 22:03 | 56,148 | +223 |
| 31 Aug 2026, 23:16 | 55,925 | +301 |
| 30 Aug 2026, 19:47 | 55,624 | +174 |
| 29 Aug 2026, 21:34 | 55,450 | +47 |
| 28 Aug 2026, 23:14 | 55,403 | +451 |
| 28 Aug 2026, 02:28 | 54,952 | +241 |
| 27 Aug 2026, 02:47 | 54,711 | +850 |
| 25 Aug 2026, 23:25 | 53,861 | -35 |
| 24 Aug 2026, 22:05 | 53,896 | +1,222 |
| 23 Aug 2026, 10:13 | 52,674 | +641 |
| 21 Aug 2026, 21:36 | 52,033 | +601 |
| 20 Aug 2026, 14:04 | 51,432 | first reading |
Engagement
64 posts held, back to 4 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 97 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.473%
- avg views ÷ 58,888 subscribers
- Avg views / post
- 279
- 35 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 35
- of 64 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 22 September 2026 |
|---|---|
| Posts held | 64 (4 July 2025 – 22 September 2026) |
| Views total | 9,752 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 15:12 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.
What this channel posts
- Photos
- 27
- Videos
- 4
- Links
- 20
Lifetime counters from Telegram’s own channel header, read 22 September 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.
- Video runtime
- 20s
- Average length
- 5s
Measured directly from 4 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.
Recent posts
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
🔎洪山区 🔎青山区 🔎武昌区 🔎汉阳区 🔎硚口区 🔎江岸区 🔎江汉区 🔎其它区 🔎外围上门~各类会所 🫂武汉交流群 📮出击报告 👇下面其它地方资源👇 ✅深圳资源 ✅广州资源 ✅杭州资源 ✅长沙资源 ✅南京资源 ✅上海资源
Showing the 12 most recent of 64 posts we hold for @haoyuane. 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 11 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.
@haoyunna · 27,24991 posts广州911(认证榜)
@Hzxiaomo · 40,35051 posts长沙911(认证榜)
@anangao · 55,82148 posts杭州911(认证榜)
@loveyou6VV · 78,97748 posts南京出击榜(先锋)
@zoudeyun · 68,43145 posts深圳911(认证榜)
@Yuoyoutan · 87,34643 posts上海911(认证榜)
@maokuanyou · 76,85540 posts东北认证资源🥇沈阳大连长春哈尔滨
@zaiaSAS · 39,54134 posts济南青岛公开资源(认证)
@sosuokV · 35,08630 posts南昌公开资源(认证)
@xiaodolS · 33,36227 posts叼
@sdkjf456f · 221 post
Names
Channels on the register whose handles appear in this channel's posts.
@anangao · 55,82154 posts武汉出击报告📮
@haoyunna · 27,24954 posts广州911(认证榜)
@Hzxiaomo · 40,35054 posts杭州911(认证榜)
@loveyou6VV · 78,97754 posts上海911(认证榜)
@maokuanyou · 76,85554 posts武汉出击先锋🎷
@mlxmrx · 68,70254 posts深圳911(认证榜)
@Yuoyoutan · 87,34654 posts南京出击榜(先锋)
@zoudeyun · 68,43154 posts全国探花(中低高端)外围
@vuvvvvvvvvv · 13,1813 posts七喜全国包养素人/全国外围大圈 - 武汉mmc 真空游戏 情趣换装场
@aammcwh111 · 21 post惠州大学城(修车)
@ccxsxs · 34,4791 post福建(福州厦门泉州)大群
@dazzqq · 36,4761 post郑州修车(交流)
@gggu_u · 34,1771 post武汉同城头条✿中转站
@i828i · 5,3001 post南京(夜游)
@ii88_8 · 34,6361 post桔子的朋友圈
@juzi100086 · 5841 post桂林学生会〠修车
@qqqm_m · 34,3971 post无锡快活林(修车)
@uvogg · 34,3991 post常州修车学院✞
@uvoww · 33,4631 post东莞理工学院
@w88_88 · 34,2511 post西安修车学院
@ww66tt · 33,6851 post郑州出击认证榜✺
@youzhiyun · 31,5921 post佛山修车(总群)
@zo_aa · 33,5531 post
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“武汉出击榜(先锋)” (@haoyuane), 58,888 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/haoyuane.
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.