Engagement
20 posts held, back to 13 April 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 16.8%
- avg views ÷ 489 subscribers
- Avg views / post
- 82.3
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 20 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.
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.
Recent posts
6 Aug 2026, 18:44 UTC2 viewsread 6 August 2026 🚀加入极搜互推一起赚钱🚀
车队:外围专用3
2.11k 接码/卡商/人脸实名/微信支付宝号
475 Cosplay🥰高清COS❤️角色扮演😘陌鱼
1.45k 🔥全国楼凤资料免费共享🔥
3.02k 深圳宝安养生会所
623 宣州区修车补课凤楼
2.09k 夫妻SPA/男技师/异性spa/私密视频💋👄
1.04k 天津外围(精选资源)
728 黄播 🍒樱桃🍒 七彩 小妲己
933 上门-约炮-同城-素材女图-修车
2.44k 珠海 95-94 海选水床丝袜【鉴黄师】
241 福利社
Signed 极搜互推
6 Aug 2026, 07:15 UTC14 viewsread 6 August 2026 Photo
🔥TeleTop 频道推荐
📢😍😍Coser图集鉴赏🥰🥰
📢少妇~熟女阁〔精品〕
📢温州蝶恋花
📢厦门福州抓龙筋 女王调教
📢北京高端外围兼职
📢广州佛山高端,江门中山95-98工作室
📢MissAV 国产日韩欧美
📢【知鸢°】全国外围 处女 学生包养
📢广州 美腿 街拍 偷拍 丝袜
📢南昌 帝王会所
💎广告推荐
📢东南亚今日头条|新闻|爆料|悬赏|通缉|...
📢182体育综合平台,电子,棋牌,百家乐,...
📢🅾️AG官网直营✅大客必备✅注册送15...
🔍互推公示 🪧流量互推说明
Signed 中文索引
3 Aug 2026, 10:31 UTC57 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
29 Jul 2026, 17:08 UTC105 viewsread 6 August 2026 🚀加入极搜互推一起赚钱🚀
车队:外围专用3
2.11k 接码/卡商/人脸实名/微信支付宝号
475 Cosplay🥰高清COS❤️角色扮演😘陌鱼
1.45k 🔥全国楼凤资料免费共享🔥
3.02k 深圳宝安养生会所
623 宣州区修车补课凤楼
2.09k 夫妻SPA/男技师/异性spa/私密视频💋👄
1.04k 天津外围(精选资源)
728 黄播 🍒樱桃🍒 七彩 小妲己
933 上门-约炮-同城-素材女图-修车
2.44k 珠海 95-94 海选水床丝袜【鉴黄师】
241 福利社
Signed 极搜互推
27 Jul 2026, 10:49 UTC123 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
20 Jul 2026, 10:46 UTC193 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
13 Jul 2026, 10:47 UTC252 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
6 Jul 2026, 10:32 UTC323 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
29 Jun 2026, 10:49 UTC374 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
22 Jun 2026, 10:32 UTC380 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
15 Jun 2026, 10:42 UTC403 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
8 Jun 2026, 10:45 UTC448 viewsread 6 August 2026 Photo
🚀帮助您找到感兴趣的群组、频道和机器人
📊频道分析 📢官方频道
Signed 中文索引
Showing the 12 most recent of 20 posts we hold for @Vip99886666. 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 — 366,222 of 1,548,671entries 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 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@Vip99886666 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@dhdncncm
named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 10 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced 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.
“西安修车大队高端自带外卖频道💋” (@Vip99886666), 489 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Vip99886666.
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.