红休啦!小哥哥们一周后见啦!

Channel
成都 亦可
@xp816016
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,964subscribers
+11 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002051654616 |
|---|---|
| Type | Channel |
| Username | @xp816016 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/xp816016 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 09:15 | 2,964 | +4 |
| 1 Sept 2026, 14:39 | 2,960 | +6 |
| 29 Aug 2026, 10:03 | 2,954 | -3 |
| 26 Aug 2026, 04:13 | 2,957 | +1 |
| 23 Aug 2026, 08:06 | 2,956 | +3 |
| 19 Aug 2026, 08:00 | 2,953 | no change |
| 19 Aug 2026, 07:45 | 2,953 | first reading |
Engagement
16 posts held, back to 31 July 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
- 21.2%
- avg views ÷ 2,964 subscribers
- Avg views / post
- 630
- 10 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 10
- of 16 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 1 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 16 (31 July 2026 – 11 August 2026) |
| Views total | 6,298 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Aug 2026, 08:00 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.
Reaction mix
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.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 3 of the 16 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 31 July 2026 to 11 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
Photo, posted without a caption
Photo, posted without a caption
今天的小确幸来源于小哥哥的高度认可,刚见面就觉得我长在了他的心尖尖上,直接转了一个见面口令红包,享受过后,又+V,转了微信红包🧧,生活再累,有你们的认可,都足以让我笑着面对…😛
Photo, posted without a caption
忙碌的一天,成功的被多次回锅的小哥哥逗乐了,以为这玩意还能再次发育……结果是我误会了😂
👅
哥哥爽快又温柔,提前就交了定金,体验了我的服务给了好好评,今天又是美美的一天😜
第一次约亦可老师,身材非常的哇塞,忍不住看的那种,大长腿又白又直,口技一流,水中萧就初见端倪,花样不少,口的很长时间,配上丝袜做的感觉很爽。
又是一个回锅的哥哥,脾气好又骚气,早课时间赶点都愿意等早早地就来给我做服务,心里老甜了😜
【时间】:2026-08-06 【老师】:亦可 【留名】:包菜 【人照】:9 【颜值】:9.5 【身材】:9 【服务】:10 【态度】:9 【环境】:9 【综合】:9.25 【过程】:亦可本人比照片更好看一些,身材完美,态度好,服务无敌好,口活爽飞了,深喉更是一绝,那种感觉前所未有。女上很不错,换姿势后顺利出货,我已经开始盘算二刷了 老师细致耐心,从事前到事后都很沉浸,体验感拉满,非常适合出击 ✳️Powered by @olddriver_cdq
四项🌹
Showing the 12 most recent of 16 posts we hold for @xp816016. 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 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“成都 亦可” (@xp816016), 2,964 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/xp816016.
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.