#频道互推 #相似推荐 ------------------------------ 📢 武汉寻花 📢 上海艳遇 📢 重庆品茶 📢 杭州花坊 📢 同城约炮.学生少妇 📢 东莞太子殿 📢 深圳 95/96SPA 精品会所|同城推荐 📢 佳佳1v1视频陪聊(可验证) 📢 全球外卖频道 📢 深圳外围【金榜阁】深圳修车 ------------------------------ ☁️ 互推入口:@sooo

Channel
柚子社(1v1/定制/举牌/原味)一对一
@Yozishe
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,820subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003322843478 |
|---|---|
| Type | Channel |
| Username | @Yozishe |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Yozishe |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 06:07 | 2,820 | -10 |
| 11 Aug 2026, 04:37 | 2,830 | +15 |
| 7 Aug 2026, 18:33 | 2,815 | no change |
| 7 Aug 2026, 18:26 | 2,815 | first reading |
Engagement
18 posts held, back to 27 June 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 78.1%
- avg views ÷ 2,820 subscribers
- Avg views / post
- 2,200
- 7 posts measured
- Reaction rate
- 0.163%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 18 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 5 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 18 (27 June 2026 – 7 August 2026) |
| Views total | 15,421 |
| Reactions total | 25 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 18: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
- 13s
- Average length
- 7s
Measured directly from 2 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
56 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 92.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 52 | 92.9% | |
| 🥰 | 3 | 5.36% | |
| 😁 | 1 | 1.79% |
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 12 of the 18 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 56reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 27 June 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
频道适合看内容,群组更适合继续交流。 SOSO 可以直接找热门群组,也能按关键词搜同类圈子。 先打开看看当前推荐。
Photo, posted without a caption
❤10
https://t.me/sesezsq/1140 给柚子投一票 拜托啦
❤2
🚪188 入门滴滴 接视频接定制 下单联系 @keaiyozi 双向联系 @keaiyouzi_bot 粉丝群 @Keaiyouzi 柚子的照片 @Yozishe 反馈频道 @Yuanweiyouzi
❤4
🚪188 入门滴滴 接视频接定制出原味 下单联系 @keaiyozi 双向联系 @keaiyouzi_bot 粉丝群 @Keaiyouzi 柚子的照片 @Yozishe 反馈频道 @Yuanweiyouzi
❤2
Posted without readable text
❤3🥰3😁1
有骗子盗我视频骗人 频道照片什么的还盗的我的 还骗了别人50u 大家避雷这个人 骗子飞机号 @hpxsy
起床啦
给柚子投一票 拜托惹˶o̴̶̷᷄‸o̴̶̷̥᷅˶ https://t.me/sesezsq/1068
❤9
接视频接定制出原味 下单联系 @keaiyozi 双向联系 @keaiyouzi_bot 粉丝群 @Keaiyouzi 柚子的照片 @Yozishe 反馈频道 @Yuanweiyouzi
❤5
分享一个福利姬频道 https://t.me/Keaifuliji 后续我再做一个我喜欢的片的频道🤎 分享交流一下
Showing the 12 most recent of 18 posts we hold for @Yozishe. 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
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“柚子社(1v1/定制/举牌/原味)一对一” (@Yozishe), 2,820 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Yozishe.
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.