Telegram RegisterThe public register of Telegram
Telegram profile photo for 绿帽单男 人妻偷情

Channel

绿帽单男 人妻偷情

@trdgnvb

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

3,807subscribers

+2,269 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003912268416
TypeChannel
Username@trdgnvb
CreatedBetween 1 April 2026 and 6 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live31 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/trdgnvb

Growth

1,5383,8072,672.57 August 2026 — 1,538 subscribers7 August 2026 — 1,538 subscribers8 August 2026 — 1,671 subscribers12 August 2026 — 2,149 subscribers15 August 2026 — 2,613 subscribers19 August 2026 — 2,966 subscribers22 August 2026 — 3,222 subscribers25 August 2026 — 3,434 subscribers28 August 2026 — 3,637 subscribers31 August 2026 — 3,807 subscribers7 August 202631 August 2026
10 measurements spanning 23 days, net +2,269. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,198–4,147 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 05:083,807+170
28 Aug 2026, 07:163,637+203
25 Aug 2026, 03:293,434+212
22 Aug 2026, 02:253,222+256
19 Aug 2026, 03:062,966+353
15 Aug 2026, 20:082,613+464
12 Aug 2026, 01:122,149+478
8 Aug 2026, 19:221,671+133
7 Aug 2026, 21:331,538no change
7 Aug 2026, 19:481,538first reading

Engagement

19 posts held, back to 6 August 2026the 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
19.6%
avg views ÷ 3,807 subscribers
Avg views / post
748
19 posts measured
Reaction rate
0.048%
reactions ÷ views · ER floor
Posts in window
19
of 19 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. It is computed over the 4 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held19 (6 August 20267 August 2026)
Views total14,208
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 21:33 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
2h 13m
Average length
16m 39s

Measured directly from 8 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.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 6 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 13:30 UTC303 viewsread 7 August 2026
Video

📱91Porn亚洲最火成人网站,强势回归!🎲 😛精选劲爆视频:剧情带感、操得又深又狠 💋10分钟内爆爽短视频:节奏快狠准、直击G点 🎲暗网猎奇资源区:刺激大胆、满足隐秘欲望(不过度) 🎲十年经典老站,全网精品国产原创视频,免费观看😍 📱点击此处一键收藏下方☺️ ☺️ 全部福利频道 ❤️ 📱精选劲爆 爆爽短视频 AI成人 猎奇‖露出 📱 标签 #成人视频 #长视频 #短视频 #猎奇资源 #黄源 #无码 #精选

7 Aug 2026, 07:36 UTC444 viewsread 7 August 2026

偷情曝光宁波姚丽敏背着老公被金主调教操完尿逼里反差性奴

7 Aug 2026, 07:36 UTC430 viewsread 7 August 2026

偷情曝光反差婊大学生背着男友与我多次无套性爱视频泄露

7 Aug 2026, 05:36 UTC501 viewsread 7 August 2026

邻居因老公常年不在家内心极度空虚被我有机可乘大肉棒直插骚穴居然还给我吞精

7 Aug 2026, 05:36 UTC486 viewsread 7 August 2026

出轨女友淫语对白反差骚货小女友给男朋友带绿帽被操到高潮

7 Aug 2026, 03:35 UTC527 viewsread 7 August 2026

花季美少女嫩妹背着男友偷情简单亲几口摸几下淫水就湿透内裤超级粉嫩小穴无毛个性爆艹

7 Aug 2026, 01:35 UTC536 viewsread 7 August 2026

和她偷情快一年了虽然不在一个家住但是楼上楼下每天约会都特别方便

7 Aug 2026, 01:35 UTC570 viewsread 7 August 2026

大型旅行社老总和下属偷情小小导游床上功夫了得高潮一波又一波

6 Aug 2026, 23:35 UTC614 viewsread 7 August 2026

淫妻出轨 老婆被连续输出个个都是猛男公狗腰操逼频率杠杠的爽的老婆不要不要的

6 Aug 2026, 23:35 UTC670 viewsread 7 August 2026
Photo

已婚少妇出轨前男友只为体验40度的肉棒

6 Aug 2026, 13:53 UTC≈1,010 viewsread 7 August 2026
Video

📱91Porn亚洲最火成人网站,强势回归!🎲 😛精选劲爆视频:剧情带感、操得又深又狠 💋10分钟内爆爽短视频:节奏快狠准、直击G点 🎲暗网猎奇资源区:刺激大胆、满足隐秘欲望(不过度) 🎲十年经典老站,全网精品国产原创视频,免费观看😍 📱点击此处一键收藏下方☺️ ☺️ 全部福利频道 ❤️ 📱精选劲爆 爆爽短视频 AI成人 猎奇‖露出 📱 标签 #成人视频 #长视频 #短视频 #猎奇资源 #黄源 #无码 #精选

Showing the 12 most recent of 19 posts we hold for @trdgnvb. 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 — 538,131 of 1,628,524entries 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“绿帽单男 人妻偷情” (@trdgnvb), 3,807 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/trdgnvb.

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.