来自速搜推荐 @SSOU 📢AG代理 AG官网 AG... 📢欧博代理 欧博正网 欧博... 📢环球360代理 环球36... 📢真人视讯:欧博|亚星百家... 📢圣淘沙真人视讯、现场同步... 📢欧博代理 亚星代理 欧博... 📢体育投注|体育下注|体育... 📢自慰 福利姬 📢成人資訊好康分享🔞 📢私密按摩spa 📢欧博官网🅱️欧博私网�... 📢百家乐代理 欧博百家乐 ... 📢💕YoYo全国高端外围 📢欧博亚星利博万利AG贵宾... 📢AG代理|AG官网|AG... 👉流量互推规则介绍💥 以下是广告推荐 📢球速体育相信品牌的力量、老品牌值得信赖、不限ip、免实名。 📢专业Telegram账号交易平台🔥热门社交媒体账号交易 📢✅东南亚大事件✅柬埔寨大事件✅东南亚新闻 📢💹567U时代火爆上线!招收玩家/代理,匿名开户,放心娱乐! 📢🥇2G.COM 品牌定位全球 实力超乎想象 🇨🇳 简体中文包 —————————--…

Channel
🔞台灣鹹濕成人外流🔞無上限版
@av0531
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
123subscribers
+87 since we began measuring on 15 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003914638592 |
|---|---|
| Type | Channel |
| Username | @av0531 |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 October 2026 |
| Last confirmed live | 20 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 20 October 2026 |
| On Telegram | t.me/av0531 |
Topic
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 15 October 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Oct 2026, 20:55 | 123 | +4 |
| 15 Oct 2026, 12:22 | 119 | no change |
| 13 Oct 2026, 03:56 | 119 | +35 |
| 2 Oct 2026, 05:15 | 84 | +45 |
| 17 Sept 2026, 09:59 | 39 | +3 |
| 15 Sept 2026, 11:47 | 36 | first reading |
Engagement
8 posts held, back to 24 September 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
- 87.8%
- avg views ÷ 123 subscribers
- Avg views / post
- 108
- 8 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 8
- of 8 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 October 2026 |
|---|---|
| Posts held | 8 (24 September 2026 – 15 October 2026) |
| Views total | 864 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 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
- Video runtime
- 3m 41s
- Average length
- 44s
Measured directly from 5 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
https://www.instagram.com/0902.mengyan/ 這是我私人的IG平時會發發日常照片這些的 哥哥們可以追一下呦
Video, posted without a caption
Video, posted without a caption
Video, posted without a caption
Video, posted without a caption
Video, posted without a caption
Photo, posted without a caption
Showing the 8 most recent of 8 posts we hold for @av0531. 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 5 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.
@agdailie1 · 41 postAG代理 AG官网 AG百家乐 AG私网
@AGSIWANG1 · 61 post真人视讯:欧博|亚星百家乐
@BBG333B · 111 post欧博亚星利博万利AG贵宾会一比一
@hgq5312 · 4451 post欧博代理 亚星代理 欧博私网 亚星私网
@huangguandaili66 · 71 post💕YoYo全国高端外围
@hzgdww1 · 321 post欧博代理 欧博正网 欧博官网 欧博私网
@kvmkbmbws · 221 post体育投注|体育下注|体育推荐|体育赛事|篮球比赛
@lanqiu1c · 31 post圣淘沙真人视讯、现场同步、百家乐龙虎牛牛
@LTJHWS · 101 post欧博官网🅱️欧博私网🅱️欧博上分🅱️欧博代理
@oubo6789 · 171 post122体育 赌王之王-PG电子/麻将胡了/AG捕鱼
@pg56984 · 40,6751 post速搜
@ssou · 161,8011 post速搜❤️🔥流量互推/广告交易
@TonAdNews · 12,9781 post环球360代理 环球360官网 环球360私网
@tygfr111 · 81 postX-Panel 社交媒体账号出售
@XPanelsell · 42,5921 post百家乐代理 欧博百家乐 亚星百家乐 利博百家乐
@yaxing22a · 51 post东南亚大事件
@yuenanU · 167,0841 post
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 20 October 2026 — this entry's latest reading, not the date you are reading this.
“🔞台灣鹹濕成人外流🔞無上限版” (@av0531), 123 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/av0531.
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.