冲喜宝贝❤️上海 年龄18 身高163 体重95 🈶门槛,口嗨勿扰 谢谢 专属客服 :@HK520520 #上海处女 #深圳处女 #香港处女 #处女空降 #开处 #破处
❤3👍1💯1

Channel
@SZchunv01
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
8,475subscribers
+721 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001290092671 |
|---|---|
| Type | Channel |
| Username | @SZchunv01 |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/SZchunv01 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 50% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 14:42 | 8,475 | +62 |
| 12 Sept 2026, 07:38 | 8,413 | +91 |
| 7 Sept 2026, 16:37 | 8,322 | +63 |
| 2 Sept 2026, 13:13 | 8,259 | +71 |
| 30 Aug 2026, 09:37 | 8,188 | +74 |
| 27 Aug 2026, 10:12 | 8,114 | +56 |
| 24 Aug 2026, 19:48 | 8,058 | +75 |
| 21 Aug 2026, 09:57 | 7,983 | +30 |
| 18 Aug 2026, 12:42 | 7,953 | +51 |
| 15 Aug 2026, 15:43 | 7,902 | +64 |
| 12 Aug 2026, 10:24 | 7,838 | +79 |
| 9 Aug 2026, 05:51 | 7,759 | +5 |
| 9 Aug 2026, 00:30 | 7,754 | first reading |
28 posts held, back to 6 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 17 pages 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. It is computed over the 3 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 28 (6 August 2026 – 27 August 2026) |
| Views total | 2,178 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 18:36 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 22 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.
17 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 64.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 64.7% | |
| 👍 | 2 | 11.8% | |
| 💯 | 2 | 11.8% | |
| 🔥 | 1 | 5.88% | |
| 🥰 | 1 | 5.88% |
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 11 of the 28 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 28 most recent posts we hold, published 6 August 2026 to 27 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.
冲喜宝贝❤️上海 年龄18 身高163 体重95 🈶门槛,口嗨勿扰 谢谢 专属客服 :@HK520520 #上海处女 #深圳处女 #香港处女 #处女空降 #开处 #破处
❤3👍1💯1
#频道互推 #相似推荐 ------------------------------ 📢 支付宝🟨陌陌⬛soul🟩交友婚恋❤【探探】 📢 郑州摩登女郎 📢 南京茶屿|大圈洋酒 📢 深圳无忧修车 📢 广州【会所】 📢 杭州老师 📢 全国妹妹包养频道 📢 广州 深圳 东莞 佛山 选妃总汇 📢 石家庄外围 石家庄上门 石家庄约炮 💕茶园夜色 📢 佛山技师 ------------------------------ ☁️ 互推入口:@sooo
冲喜宝贝❤️ 长沙 身高162 年龄15 体重85 🈶门槛 口嗨勿扰 谢谢 专属客服:@HK520520 #长沙处女 #深圳处女 #香港处女 #处女空降 #破处 #开处
👍1💯1🥰1
冲喜宝贝❤️广州 年龄18 身高161 🈶门槛 口嗨勿扰 专属客服 :@HK520520 #广州处女 #深圳处女 #处女空降 #开处 #破处 全国处女
冲喜宝贝❤️长沙 年龄17 身高163 🈶门槛 口嗨勿扰 谢谢 专属客服 :@HK520520 #长沙处女 #深圳处女 #天津处女 石家庄处女 #保定处女 #广州处女 #开处 #破处
❤1
冲喜宝贝❤️ 南昌 身高166 年龄16 极品新人报道,多多关照 🈶门槛 口嗨勿扰 专属客服 :@HK520520 #南昌处女 #深圳处女 ##开处 #破处 全国处女 #处女空降
冲喜宝贝❤️广州 年龄16 身高165 🈶门槛 口嗨勿扰 ❤️❤️❤️ 专属客服 :@HK520520 #广州处女 #深圳处女 #石家庄处女 #天津处女 #保定处女 #全国处女 #处女空降 #开处 #破处
冲喜宝贝❤️广州 ❤️年龄16 ❤️身高163 ❤️听话 🈶门槛 口嗨勿扰 专属客服 :@HK520520 #广州处女 #深圳处女 #石家庄处女 #天津处女 #保定处女 #处女空降 #全国处女 #开处 #破处
❤1
冲喜宝贝❤️深圳 身高165年龄16 🈶门槛 口嗨勿扰 专属客服 :@HK520520 #深圳处女 #深圳找处女 #找处女 #开处 #破处 #福田处女 #南山处女 #罗湖处女
❤1
冲喜宝贝❤️ 深圳 年龄17身高169 🈶门槛 口嗨勿扰 专属客服 :@HK520520 #深圳处女 #全国处女 #开处 #破处 #处女空降
❤3
https://t.me/soso?start=boost_SZchunv01_7427149698 ⚡️ 帮「深圳处女(🉑空降)」助力一下 点开 SOSO 即可完成,更多助力有助于获得更多搜索曝光。
冲喜宝贝❤️ 长沙 身高162年龄18 甜美可爱得小处女 🈶门槛 口嗨勿扰 专属客服 :@HK520520 #长沙处女 #深圳处女 #石家庄处女 #保定处女 #天津处女 #开处 #破处
Showing the 12 most recent of 28 posts we hold for @SZchunv01. 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.
@SZchunv01 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳处女(🉑空降)” (@SZchunv01), 8,475 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/SZchunv01.
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.