Telegram RegisterThe public register of Telegram

Channel

深圳赏颜阁公开榜

@rcrczz

2 usernames

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

29,718subscribers

+227 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002990345417
TypeChannel
Usernames@rcrczz @szsyg3
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/rcrczz

Growth

29,49129,73329,6126 August 2026 — 29,491 subscribers6 August 2026 — 29,496 subscribers7 August 2026 — 29,508 subscribers7 August 2026 — 29,543 subscribers8 August 2026 — 29,555 subscribers8 August 2026 — 29,680 subscribers9 August 2026 — 29,687 subscribers9 August 2026 — 29,733 subscribers10 August 2026 — 29,703 subscribers10 August 2026 — 29,630 subscribers11 August 2026 — 29,638 subscribers11 August 2026 — 29,654 subscribers12 August 2026 — 29,655 subscribers12 August 2026 — 29,676 subscribers13 August 2026 — 29,697 subscribers13 August 2026 — 29,718 subscribers29,7186 August 202613 August 2026
16 measurements spanning 7 days, net +227. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 29,455–29,769 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:3729,718+21
13 Aug 2026, 00:3829,697+21
12 Aug 2026, 12:5429,676+21
12 Aug 2026, 01:4229,655+1
11 Aug 2026, 16:2329,654+16
11 Aug 2026, 03:1829,638+8
10 Aug 2026, 16:2629,630-73
10 Aug 2026, 03:3229,703-30
9 Aug 2026, 19:2129,733+46
9 Aug 2026, 03:5129,687+7
8 Aug 2026, 19:2229,680+125
8 Aug 2026, 04:5529,555+12
7 Aug 2026, 19:0129,543+35
7 Aug 2026, 06:4129,508+12
6 Aug 2026, 22:4529,496+5
6 Aug 2026, 20:1729,491first reading

Engagement

47 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.55%
avg views ÷ 29,718 subscribers
Avg views / post
462
47 posts measured
Reaction rate
0.154%
reactions ÷ views · ER floor
Posts in window
47
of 47 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 8 of 47 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held47 (6 August 202613 August 2026)
Views total21,704
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 10:26 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
2m 36s
Average length
11s

Measured directly from 14 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

6 reactions across 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6100.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 8 of the 47 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 47 most recent posts we hold, published 6 August 2026 to 13 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

13 Aug 2026, 06:04 UTC181 viewsread 13 August 2026
Photo

✅花名:#婉月 😘水费:#1000p 📍地区:#福田 🧑‍🩰身高: 172 罩杯:B 💎标签:#嫩妹 #kiss #六九 ✈️电报:@szwanyue ☎️双向:@szwanyueBot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

13 Aug 2026, 05:38 UTC200 viewsread 13 August 2026
Photo

✅花名:#柳岩 😘水费:#1500p 📍地区:#福田 🧑‍🩰身高: 170 罩杯:E 💎标签:#嫩妹 #蛇吻 #鸳鸯浴 ✈️电报:@Lyan2828 ☎️双向:@Lyan21_bot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

13 Aug 2026, 04:51 UTC204 viewsread 13 August 2026
Photo

✅花名:#呆瓜 😘水费:#700p 📍地区:#宝安 🧑‍🩰身高: 162 罩杯:B 💎标签:#嫩妹 #蛇吻 #六九 ✈️电报:@daiguaz ☎️双向:@daiguasbot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

13 Aug 2026, 04:45 UTC188 viewsread 13 August 2026
Photo

✅花名:#Lulu 😘水费:#1400P 📍地区:#福田 🧑‍🩰身高:165 👙罩杯:D 💎标签:#嫩妹 #蛇纹 #六九 #白虎 ✈️电报:@LuLu521314 ☎️双向:@TeijhBiu_bot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

12 Aug 2026, 14:57 UTC≈1,080 viewsread 12 August 2026
Photo

🎉 温碧霞老师半价劵福利 🎁 奖品清单 • 单P半价劵 × 1 • 单P100优惠卷 × 5 • 双P200优惠卷 × 5 🛡️ 参与条件 • 加入 深圳赏颜阁 • 加入 深圳赏颜阁(轮播) • 加入 深圳赏颜阁(备用) • 加入 深圳赏颜阁公开榜 • 必须设置用户名 🔮 祝福加持 • 祝福消耗:50肾结石 • 祝福上限:100次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 开奖时间 • 2026-08-15 12:00:00 📜 抽奖说明 优惠卷有效期(7天) 半价卷有效期(5天) 白嫖卷有效期(3天) 禁止转让,私下交易买卖 发现永久取消中奖资格 中奖自行联系 @jiaqi6886 ✨ 愿好运伴随每一位参与者,祝大家好运!

12 Aug 2026, 13:39 UTC≈1,180 viewsread 12 August 2026

@asd456151 南山(晨晨) 200通用优惠卷*5 先抢先得,需要私信老师!

12 Aug 2026, 12:13 UTC281 viewsread 12 August 2026
Photo

✅花名:#文静 #抓龙筋 😘水费:#599P 📍地区:#福田 🧑‍🩰身高:168 罩杯:D 💎标签:#嫩妹 ✈️电报:@w66552211 ☎️双向: 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

12 Aug 2026, 11:58 UTC237 views1 reactionsread 12 August 2026
Photo

✅花名:#芊芊 😘水费:#688P 💎标签:#嫩妹 📍地区:#福田 🧑‍🩰身高:168 👙罩杯:D ✈️电报:@quanqian688 ☎️双向:@quanqian688bot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

1

12 Aug 2026, 10:40 UTC286 viewsread 12 August 2026
Photo

✅花名:#温碧霞 😘水费:#800P 📍地区:#福田 🧑‍🩰身高:165罩杯:F 💎标签:#御姐 ✈️电报:@jiaqi6886 ☎️双向:@jiaqi6886_bot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

12 Aug 2026, 07:10 UTC81 viewsread 12 August 2026
Photo

✅花名:#芊艺 😘水费:#1300P 📍地区:#罗湖 🧑‍🩰身高:163罩杯:B 💎标签:#嫩妹 #kiss #六九 ✈️电报:@qianyilh ☎️双向:@qianyilhbot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

12 Aug 2026, 06:19 UTC129 views0 reactionsread 12 August 2026
Photo

✅花名:#江月诗 😘水费:#1200P 📍地区:#南山 🧑‍🩰身高:166 罩杯:B 💎标签:#嫩妹 #kiss #六九 ✈️电报:@P07bm ☎️双向:@lm007ibot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

12 Aug 2026, 05:26 UTC169 viewsread 12 August 2026
Photo

✅花名:#沅一一 😘水费:#900p 💎标签:#御姐 📍地区:#罗湖 🧑‍🩰身高:161 👙罩杯:C ✈️电报:@yiyi636 ☎️双向:@yy866_bot 深圳赏颜阁: @szsyg1 上榜机器人: @hajimi11_bot 车评机器人: @qwglbot 写车评获取出击码参与抽奖

Showing the 12 most recent of 47 posts we hold for @rcrczz. 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.

Citation-graph rank

Citation-graph rank — 76,260 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 18 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.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“深圳赏颜阁公开榜” (@rcrczz), 29,718 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/rcrczz.

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.