全国林妹高端外围【大⭕️】 #定金预约 本群可担保 💎专注各市区修车 🈶洋马,空姐,少妇,萝莉, 御姐等高素质高颜值🉑上门 🈶教室 ✡️奢华的环境、全套服务、至尊享受、帝王体验 ♏️联系客服情妹: @lingmei888168 ♏️双向客服林妹: @wai998bot ♒️总频道: https://t.me/yewuzuvip #本群推荐信誉客服

Channel
贵阳骑行榜
@qixingdui74
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
19,937subscribers
-145 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003098198514 |
|---|---|
| Type | Channel |
| Username | @qixingdui74 |
| Description | 【唯一管理】: @xiaoji888bot 【骑行榜】老师频道;https://t.me/qixingdui74 【骑行大队】交流群: https://t.me/kumqix75 【全国公用防骗曝光榜】:https://t.me/bikan888 |
| Created | Between 1 September 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/qixingdui74 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:16 | 19,937 | -116 |
| 13 Aug 2026, 04:18 | 20,053 | -29 |
| 12 Aug 2026, 17:32 | 20,082 | first reading |
Engagement
7 posts held, back to 5 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 7 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 10.5%
- avg views ÷ 19,937 subscribers
- Avg views / post
- 2,100
- 7 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 7
- of 7 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 15 August 2026 |
|---|---|
| Posts held | 7 (5 August 2026 – 15 August 2026) |
| Views total | 14,720 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 09:20 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
- 204
- Videos
- 35
- Links
- 19
Lifetime counters from Telegram’s own channel header, read 15 August 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
- 1s
- Average length
- 1s
Measured directly from 1 video 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
🟡昵称: #惠子 🕐地区: #云岩区 🤖双向:@huihui9099botbot 🚀电报:@huizi9990 🔴水费:📤课表查看图📤
到贵阳,找可乐海选会所,全场499 驻场模特599,老司机不迷路,新手不踩坑玩的开心玩的放心帝王待遇。 按摩/半套/推油/油压 十多年老团队 五星环境 关系稳定,设施齐全,颜值担当 私密安全 安全保障 明码标价 无办卡 无套路 方便停车 出入安心 各种制服 主题剧情 开背指划 胸滑捞月 过水毒龙 丝滑乳交 漫游冰火 女王调教 水摩拉丝 丝足骑士 手T+胸T+足T+腿T+舌电+漫游+独龙 价格:499 分牌分颜值海选每天不固定兼职学生妹模特做599 统一服务60分钟 出水限时不限次数 双飞统一加200 两人同行优惠50 三人同行优惠100 四人同行优惠200 五人及以上每人优惠100 每次走了给我发次数累计,第五次全场半价300买单 #贵阳 #观山湖 #南明 #云岩 #白云 #花溪 营业时间:中午12:00-凌晨4:00 出勤20多位03…
🟡昵称: #沫希 🕐地区: #花果园 🤖双向: 🚀电报:@moxiii01 🔴水费:📤课表查看图📤
🟡昵称: #私影 🕐地区: #观山湖 🤖双向: 🚀电报:@gshnvsy 🔴水费:📤课表查看图📤
#潘姐高端极品【大⭕️】 #诚信客服 已验证 #定金预约 群管已担保 💎专注特区一线城市修车,纯一手资源 只有你想不到的,没有我没有的。 ✡️奢华的环境、全套一条龙服务、至尊享受、帝王体验 ♒️总频道: @hnanjingjujidi ♏️客服潘姐: @panjie888168bot
🟡昵称: #小婉 🕐地区: #观山湖区 🤖双向:@jinyu77bot 🚀电报:@jinyuta 🔴水费:📤课表查看图📤
Showing the 7 most recent of 7 posts we hold for @qixingdui74. 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.
Citation-graph rank
Citation-graph rank — 1,305,024 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 1 registered channel — 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“贵阳骑行榜” (@qixingdui74), 19,937 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/qixingdui74.
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.