👤 #KK哥 #人妻露脸 【你的KK哥】《89年人妻》第七部 半露脸,超清画质,疯狂揉搓大奶子,好爽好刺激高潮了 ◉ 原创:#你的KK哥 ◉ 类型: 至尊|编号:6305 ▪️ 视频:1V ▪️ 时长:16分

Channel
绿帽淫妻【原创资源社区】主频道
@vvss2024
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10,128subscribers
-608 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003831963386 |
|---|---|
| Type | Channel |
| Username | @vvss2024 |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/vvss2024 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 11:36 | 10,128 | -85 |
| 13 Aug 2026, 04:33 | 10,213 | -49 |
| 12 Aug 2026, 03:42 | 10,262 | -57 |
| 11 Aug 2026, 01:37 | 10,319 | -85 |
| 9 Aug 2026, 23:35 | 10,404 | -105 |
| 8 Aug 2026, 21:56 | 10,509 | -123 |
| 7 Aug 2026, 20:51 | 10,632 | -104 |
| 6 Aug 2026, 21:58 | 10,736 | no change |
| 6 Aug 2026, 19:51 | 10,736 | first reading |
Engagement
12 posts held, back to 1 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 16 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.462%
- avg views ÷ 10,128 subscribers
- Avg views / post
- 46.8
- 12 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 12
- of 12 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 9 August 2026 |
|---|---|
| Posts held | 12 (1 August 2026 – 9 August 2026) |
| Views total | 561 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 05:19 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
- Video runtime
- 1h 24m
- Average length
- 7m 04s
Measured directly from 12 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
APP今日重磅更新 8月8日 小绿帽投稿【云南勃起哥】《淫妻与消防员单男》 哦弟弟你的鸡巴太爽了,顶得姐姐好舒服,以后姐姐就是你的骚逼,勃起哥见状鸡巴硬得不行,直接开舔弟弟的肛门,这对夫妻真是绝配 由于资源敏感 本系列不在电报更新 请下载 小绿帽APP 👉 Lvmao.app
👤 #3P极品 人气约啪博主【古河君】8月最新流出 约啪调教3P极品反差软萌等多位女主 ◉ 原创:#古河君 ◉ 类型: 公开 |编号:6303
👤 #肛门 【原创KK】全集03《舔主人的肛门》 ◉ 原创:#原创KK ◉ 类型: 主区|编号:6302 ▪️ 视频:2V ▪️ 时长:22分
👤 #淫妻3P #老A8 良家约炮大神【无敌小旋风】《第一次带淫妻3P》完美露脸 人妻喜欢玩3P ,两个鸡巴伺候的很满意,浪叫不止爽炸 ◉ 原创:#无敌小旋风 ◉ 类型: 公开|编号:6304
👤 #CK8 【中原炮王】CK-8,露脸喷水女王,8月近期最新视频第二弹 完美露脸,那骚婊子欲求不满的表情绝了 ◉ 原创:#中原炮王 ◉ 类型: 公开 |编号:6301
👤 #CK8 【中原炮王】CK-8,露脸喷水女王,8月近期最新视频第二弹 完美露脸,那骚婊子欲求不满的表情绝了 ◉ 原创:#中原炮王 ◉ 类型: 公开 |编号:6301
👤 #母狗属性 【S级人妻泄密】穷人女神富人精盆,7月流出 高颜值顶级身材美女露脸性爱自拍,母狗属性拉满 ◉ 原创:#S级泄密 ◉ 类型: 公开 |编号:6119
👤 #天津单男 天津原创【淫妻猫猫】全集03 《鸡巴被锁上》 跪在门口, 透过门缝看强壮的绿主干我老婆 俩人居然十指相扣, 单男都射精了,我还被锁着 ◉ 原创:#淫妻猫猫 ◉ 类型: 主区 |编号:6115 ▪️ 视频:1V ▪️ 时长:10分钟
👤 #桃子 【我的枪好长】全集:7月18日作品 《桃子快被我兄弟干晕了》上集 掰开腿,狗骑式暴力抽插🐍蛇袜女友 插的骚屁股撅的高高的,小穴迎着鸡巴就张开了 ◉ 原创:#我的枪好长 ◉ 类型: 主区 |编号:6116 ▪️ 视频:1V ▪️ 时长:10分钟
👤 #咩咩小可爱 人气博主【小宝】(咩咩小可爱)全集74 《初尝处南小哥哥手足口并用上了》7月19日作品 小哥哥纹丝不动 好难榨汁 ◉ 原创:#小宝 ◉ 类型: 公开 |编号:6117
👤 #白袜 推特原创【Gxtimer】全集,第12弹 JK过膝白袜 铁粉说非常喜欢看这个女神被狠狠的羞辱调教 要各种姿势体位语言骚话 ◉ 原创:#Gxtimer ◉ 类型: 主区 |编号:6118 ▪️ 视频:1V ▪️ 时长:42分钟
Showing the 12 most recent of 12 posts we hold for @vvss2024. 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,110,865 of 1,340,412entries 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.
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.
“绿帽淫妻【原创资源社区】主频道” (@vvss2024), 10,128 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/vvss2024.
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.