Channel
@szsz6658
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
61subscribers
+1 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002093839978 |
|---|---|
| Type | Channel |
| Username | @szsz6658 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/szsz6658 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 09:53 | 61 | +1 |
| 31 Aug 2026, 15:15 | 60 | no change |
| 31 Aug 2026, 15:01 | 60 | first reading |
3 posts held, back to 29 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 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.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 3 (29 August 2026 – 30 August 2026) |
| Views total | 21 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 15: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.
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.
名字：#豆豆 地区：#深圳 #宝安区 #宝安 价格：#800P #1500PP 资料：年龄18岁 身高165 体重90 胸C 联系：#ID20260831001 @ddou2008 @ddou2008bot 频道: https://t.me/doudou2028 potato土豆: 与你号: QQ:微信: uuuTalk号： 标签: #嫩妹 #六九 #舌吻 #深喉 #口爆 #包时 #深圳资源 #深圳上课 #深圳老师 #深圳修车 #深圳集美 备注: 新人待验 来源: 广东家族 @szmx01 @aihaogd @szdy11 上榜 提交报告 @shenz11145bot 深圳报告 当日开课老师目录 友群 @aihaoheiche2 @muxinh 深圳福利频道2 https://t.me/+lmHRAD-MQwM0NWVl
名字：#初初 地区：#深圳 #宝安区 #宝安 价格：#900P #1800PP 资料：年龄23身高160 体重98胸34B 联系：#ID20260830001 @opo8op @Aop6bot 频道: https://t.me/opop8op potato土豆: 与你号: QQ:微信: uuuTalk号： 标签: #嫩妹 #六九 #舌吻 #陪浴#kiss #可蛇可六九 #深圳资源 #深圳上课 #深圳老师 #深圳修车 #深圳集美 备注: 新人待验 来源: 广东家族 @szmx01 @aihaogd @szdy11 上榜 提交报告 @shenz11145bot 深圳报告 当日开课老师目录 友群 @aihaoheiche2 @muxinh 深圳福利频道2 https://t.me/+lmHRAD-MQwM0NWVl
https://t.me/szsz6658/2979 名字：#清予 地区：#深圳 #福田区 #福田 价格：#1200P #2100PP 资料：年龄25体重100胸围C身高168 联系：#ID20260828001 @yuer820 在深圳开课 💍
Showing the 3 most recent of 3 posts we hold for @szsz6658. 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.
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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳福利频道” (@szsz6658), 61 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/szsz6658.
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.