Telegram RegisterThe public register of Telegram
Telegram profile photo for 野寻.武汉修车档案

Channel

野寻.武汉修车档案

@chasewh_xcda

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

5,541subscribers

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1004416769474
TypeChannel
Username@chasewh_xcda
Description👤 唯一管理:@chase_xh_bot 📝 作业投稿: @chasehwxc_bot ——————————— 💗野寻 • 榜单结构: https://t.me/wh_xxoo/10
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 October 2026
Last confirmed live8 October 2026
Measurements held1
On Telegramt.me/chasewh_xcda

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 12:225,541first reading

Engagement

5 posts held, back to 8 October 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
1.77%
avg views ÷ 5,541 subscribers
Avg views / post
98.2
5 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
5
of 5 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 October 2026
Posts held5 (8 October 2026 – 8 October 2026)
Views total491
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Oct 2026, 12:22 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
580
Videos
97
Links
125

Lifetime counters from Telegram’s own channel header, read 8 October 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
22s
Average length
11s

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.

Recent posts

8 Oct 2026, 11:35 UTC64 viewsread 8 October 2026
Photo

🎰 甜梨白嫖卷(原西施) 📮 参与条件: 🌏️ 归属地 湖北 🎫 加入-野寻.武汉修车档案 🎫 加入-野寻.武汉打卡通告群 └ 🔑 发送口令﹝甜妹也有咸的地方﹞ 🎫 加入-野寻.武汉学生交流群 └ 🎟️ 发言数大于 666 条 🎫 加入-野寻.武汉精选榜单 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 甜梨(原西施)头课白嫖卷一张 × 1 ⚠️ 抽奖说明: 为了庆祝甜梨妹妹(原西施)入住野寻,特推出白嫖头课优惠卷一张,中奖者私信@chase_xh 联系老师确定时间安排,如自己时间问题约不上头课可约后面的,如放老师鸽子此票作废 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年10月11日 22时01分00秒

8 Oct 2026, 11:09 UTC64 viewsread 8 October 2026
Photo

♥️ CHASE | ♡ WUHAN 💌 0条车评,综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 艺名 : #小薇 地区 : #洪山区 白沙洲 数据 : 23_165_45_B 价格 : #6P #10PP #YE 服务 : #共浴 #69 #舌吻 标签 : #萝莉小纯 #兼职学生 #嫩妹系 🌍 联系方式 : 点击获取小薇联系方式 约课备注"野寻推荐" ✉️ 评价老师 : 点击评价 短期兼职,模特身材,乖巧听话懂配合 💌 作业评价 💌 工兵活动 💌 武汉交流 💌 会员制度

8 Oct 2026, 08:04 UTC104 viewsread 8 October 2026
Photo

♥️ CHASE | ♡ WUHAN 💌 0条车评,综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 艺名 : #小乖欣 地区 : #洪山区 数据 : 22_162_44_C 价格 : #6P #11PP #YE 服务 : #共浴 #可外出 #舌吻 标签 : #肤白 #纯欲系 #蜜臀 🌍 联系方式 : 点击获取小乖欣联系方式 约课备注"野寻推荐" ✉️ 评价老师 : 点击评价 邻家妹妹,长相甜美纯欲,身材高挑比例好 💌 作业评价 💌 工兵活动 💌 武汉交流 💌 会员制度

8 Oct 2026, 07:55 UTC135 viewsread 8 October 2026
Photo

♥️ CHASE | ♡ WUHAN 💌 0条车评,综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 艺名 : #甜梨 地区 : #武昌区 数据 : 20_164_43_A 价格 : #7P #14PP #YE 服务 : #共浴 #角色扮演 #舌吻 标签 : #萝莉小纯 #蜜臀 #嫩妹系 🌍 联系方式 : 点击获取甜梨联系方式 约课备注"野寻推荐" ✉️ 评价老师 : 点击评价 本人可甜可御,性格温柔爱笑,有点腼腆,喜欢主动的哥哥 💌 作业评价 💌 工兵活动 💌 武汉交流 💌 会员制度

8 Oct 2026, 05:47 UTC124 viewsread 8 October 2026
Photo

♥️ CHASE | ♡ WUHAN 💌 0条车评,综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 艺名 : #柠檬兔 地区 : #洪山区 数据 : 19_162_46_B 价格 : #8P #13PP #YE 服务 : #共浴 #可外出 #舌吻 标签 : #萝莉小纯 #兼职学生 #嫩妹系 🌍 联系方式 : 点击获取柠檬兔联系方式 约课备注"野寻推荐" ✉️ 评价老师 : 点击评价 刚开始做,没什么经验,只要不是特别恶心的都愿意配合 💌 作业评价 💌 工兵活动 💌 武汉交流 💌 会员制度

Showing the 5 most recent of 5 posts we hold for @chasewh_xcda. 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 9 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.

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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“野寻.武汉修车档案” (@chasewh_xcda), 5,541 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/chasewh_xcda.

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.