已开课哦宝子们

Channel
怡宝bao的小窝
@yibao16879
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
92subscribers
+62 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003892454578 |
|---|---|
| Type | Channel |
| Username | @yibao16879 |
| Created | 21 August 2026 — measured — dated from the channel’s first post |
| First recorded | 23 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/yibao16879 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 02:37 | 92 | +11 |
| 30 Aug 2026, 11:45 | 81 | +29 |
| 24 Aug 2026, 10:39 | 52 | +22 |
| 23 Aug 2026, 11:00 | 30 | first reading |
Engagement
7 posts held, back to 21 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
- 261.6%
- avg views ÷ 92 subscribers
- Avg views / post
- 241
- 6 posts measured
- Reaction rate
- 1.06%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 7 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 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 23 August 2026 |
|---|---|
| Posts held | 7 (21 August 2026 – 23 August 2026) |
| Views total | 1,444 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Aug 2026, 11: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.
What this channel posts
- Video runtime
- 8s
- Average length
- 8s
Measured directly from 1 video 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 1 post, 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 1 of the 7 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 7 most recent posts we hold, published 21 August 2026 to 23 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
❤2
【妹子花名】:怡宝 【联系方式】:@yywy169 【验证留名】:吊炸三国 【验证时间】:8.21 【是否中介】:有两台设备 【颜值皮肤】: 黄皮 【年龄凶器】:18左右 【身高身材】:A,偏瘦 【服务内容】:🐍,口,做 【总体感受】:整体长相7分左右,160左右身高,看到有工兵报告,而且还是嫩妹就申请出击了,在老师指导下来到高级酒店,老师打开门看到左手受伤了,听说是开车摔倒跌的,看着还是挺心疼的,老师虽然受伤还是很努力的完成每一项服务,而且还觉得因为自己受伤没做好向我表示歉意,带小雨伞前老师还有一手用里面油对小弟弟进行一次按摩,接着带上雨伞开始出击,老师妹妹十分紧有几次都把老师弄疼了,听老师说因为受伤好久没有爱爱了,女上位也略显生疏。我在一次次冲击下,被缴械了。整体虽然老师受伤了,但还是很认真态度也很好。是一个挺不错的老师
Posted without readable text
手在养伤😩不能太激烈哇请温柔对待咯
Video, posted without a caption
Channel created
Showing the 7 most recent of 7 posts we hold for @yibao16879. 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“怡宝bao的小窝” (@yibao16879), 92 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/yibao16879.
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.