新到女孩 智利🇨🇱

Channel
合肥优优日韩女孩🛀💡异国风情
@hanrbingxo809
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
294subscribers
+56 since we began measuring on 25 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003696895609 |
|---|---|
| Type | Channel |
| Username | @hanrbingxo809 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/hanrbingxo809 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 19:59 | 294 | +56 |
| 25 Sept 2026, 11:22 | 238 | no change |
| 25 Sept 2026, 10:47 | 238 | first reading |
Engagement
15 posts held, back to 24 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 54.5%
- avg views ÷ 294 subscribers
- Avg views / post
- 160
- 10 posts measured
- Reaction rate
- 0.558%
- reactions ÷ views · ER floor
- Posts in window
- 10
- of 15 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 2 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 September 2026 |
|---|---|
| Posts held | 15 (24 August 2026 – 25 September 2026) |
| Views total | 1,601 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Sept 2026, 11: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.
Reaction mix
9 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 5 | 55.6% | |
| ❤ | 3 | 33.3% | |
| 🔥 | 1 | 11.1% |
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 15 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 24 August 2026 to 25 September 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
在线, 新加波 双向 @habtruyu_bot 联系 @yuyurht
加新人到,3位都在线 日本🇯🇵女孩
态度很重要,玩性价比,
地址:必胜客(信达乐活街精选店)
人照一至,主打服务
新到女孩 智利🇨🇱
有大哥过来吗?包夜优惠情绪价格拉满,服务态度能做到99%
👍1🔥1
全套优惠200 包夜优惠300
在线, 新加波 双向 @habtruyu_bot 联系 @yuyurht
👍2
【老师艺名】优优 【联系方式】 @yuyurht 【所在位置】包河 【验证留名】匿名 【验证时间】8.23 【修车费用】1200全套 【颜值身材】颜值8分,身材10分 【服务内容】舌吻69 【服务态度】9.5 【优点缺点】优点:态度没得说,颜值可以,。 【推荐程度】10 【体验细节】遥控上楼 由于可心老师也是刚到 所以也是楼上等着老师一起进门。 人照一致 。由于时间充裕 也不着急 简单沟通翻译 然后才去洗澡 老师洗澡帮忙搓背会所一样,不急不催, 感受的柔软的奶子在身后游荡 清洗完 也是给了个温柔的水中萧。到了房间 也是激情的蛇吻 享受着老师的服务 随后也是在老师的带领下 解锁了很多姿势 女上 摇摇车(这个真的顶不住) 女上侧入(包裹感很强 还能看着奶子抖动 视觉冲击很强) 女上后入老师没力后翻身压下 囸的老师连连求饶 中间休息时 也抱着聊聊天 时不时的蛇吻 快乐的时间总是特别快,最后也是洗洗 抱抱走人 。还没体验过的值得一试,也…
❤3👍1
共享频道的
Showing the 12 most recent of 15 posts we hold for @hanrbingxo809. 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“合肥优优日韩女孩🛀💡异国风情” (@hanrbingxo809), 294 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/hanrbingxo809.
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.