Photo, posted without a caption

Channel
沈之夏天然E罩杯
@zl1688138
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
219subscribers
+186 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003906747852 |
|---|---|
| Type | Channel |
| Username | @zl1688138 |
| Created | 20 August 2026 — measured — dated from the channel’s first post |
| First recorded | 21 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/zl1688138 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 03:03 | 219 | +78 |
| 22 Aug 2026, 12:45 | 141 | +108 |
| 21 Aug 2026, 05:15 | 33 | first reading |
Engagement
5 posts held, back to 20 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
- 28.9%
- avg views ÷ 219 subscribers
- Avg views / post
- 63.3
- 4 posts measured
- Reaction rate
- 1.14%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 5 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 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 August 2026 |
|---|---|
| Posts held | 5 (20 August 2026 – 21 August 2026) |
| Views total | 253 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Aug 2026, 05:15 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
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 5 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 20 August 2026 to 21 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
🎰 福田沈之夏p半价 📮 参与条件: 🎫 加入-沈之夏天然E罩杯 🎫 加入-深圳修车出击大队【免费上榜】 🎫 加入-深圳修车出击大队【备用榜】 🎫 加入-深圳修车出击大队【轮播群】 🎫 加入-深圳修车出击大队【备用导航群】 🎫 加入-深圳修车出击大队【榜单】 🎫 加入-深圳修车出击大队【报告】 🎁 奖品内容: 💰️ P半价优惠券 × 1 ⚠️ 抽奖说明: 老师不兑换者,曝光各大群,差评处理不诚信,半价给得起要玩得起。 半价能不交定金就不交,定金最多50-100,小心骗定金。 半价三天有效期,不可以转让,需要写报告,报告投稿👉🏻 @SZ_VIPVIP 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月23日 12时31分00秒
新人开课第一天
🔥深圳茶楼不定期举行🧧活动,26年千元现金邀请活动已结束,新年红包活动已结束,四五双节千元活动已结束,端午父亲现金🧧活动已结束,后续活动择日进行~~ https://t.me/vip40f 深圳榜 https://t.me/zhenzhenchalou
❤1
Channel created
Showing the 5 most recent of 5 posts we hold for @zl1688138. 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 3 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.
@lotterynav · 169,7701 post深圳修车出击大队【备用导航群】
@SZ_xccjdadui · 5,6371 post深圳修车出击大队【免费上榜】
@SZ_xccjdd · 26,4621 post深圳修车出击大队【备用榜】
@szxiuchechuji_bd · 6,4681 post深圳修车出击大队【报告】
@SZxiuchechuji_bg · 17,1101 post深圳修车出击大队【轮播群】
@SZxiuchechuji_lb · 13,4361 post深圳修车出击大队【榜单】
@SZxiuchechuji_zy · 28,3511 post深圳茶楼
@vip40f · 21,9031 post深圳榜
@zhenzhenchalou · 23,3071 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“沈之夏天然E罩杯” (@zl1688138), 219 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/zl1688138.
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.