Telegram RegisterThe public register of Telegram

Channel

惠州工兵锐评作业榜

@RPzy_9

On this record: Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry

4,917subscribers

+32 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002173484473
TypeChannel
Username@RPzy_9
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/RPzy_9

Growth

4,8854,9174,9016 August 2026 — 4,885 subscribers7 August 2026 — 4,891 subscribers10 August 2026 — 4,909 subscribers13 August 2026 — 4,917 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +32. 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 4,880–4,922 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:354,917+8
10 Aug 2026, 08:374,909+18
7 Aug 2026, 10:184,891+6
6 Aug 2026, 23:014,885first reading

Engagement

37 posts held, back to 2 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 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
20.8%
avg views ÷ 4,917 subscribers
Avg views / post
1,020
37 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
37
of 37 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held37 (2 August 202611 August 2026)
Views total37,920
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:08 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.

Recent posts

11 Aug 2026, 17:01 UTC400 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:丁真 探险时间:8月10 探险目标:#米宝 探险坐标:#河南岸 探险花费:p 探险体验:🤓2返米宝,黄白皮,身形非频道里的大只马 真人小只马,颜值比频道好看太多,身材方面是小微胖 并不是坦克那种胖,腿型不是那种筷子腿 但架不住她肤白,胸型b+不下垂,乳头粉嫩,腰部细节有点小肚子,屁股有肉嘟感明显,情绪价值充足,递水递烟递拖鞋,女友感强烈up+,🤓但这次返食丁真的第1感觉是老师有点憔悴,我还以为不开心什么的以为半价要下菜,实则不然,能感受到老师应该是累的。好,说服务方面:帮洗帮擦、吸蛋舔咪咪调情,床上跳跳糖口 口的时间还算小长(这次齿感没前2次明显了),随后女上起手,表情投入,主动抓我手摸胸,翻身传教抽插呈痛苦表情。🤓大的要来了,米宝提出后入 结果不到2分钟小丁真直接软塌,然后重启了

11 Aug 2026, 17:01 UTC400 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:沉默工兵 探险时间:8.11 探险目标:#糯米 探险坐标:#逼贵园 探险花费:600 探险体验:吃个嫩 探花锐评:新上的嫩妹,看频道照片挺真实起码不是ai照,说是第一天都没人去,那就自己开盲盒了。开门烟味很重,好在人照一致,娇小玲珑还不错。开口牙齿难看,很严重的烟屎牙,扣分,脱衣黄皮疤痕多,很瘦但是肚子很大很凸,老师说酒喝多了有点啤酒肚。服务正常xcz,口硬带套,女上不会,对着镜子不肯,无声妖姬,拼命加速也不叫,双打变男单,没意思 综合数据:#人照 5 #芳龄:18 #颜5 #身高: 155 #胸器:a 探险评级:# 丁【甲=天菜 乙=优秀 丙=普通 丁=勉强 雷=拉垮】 联系方式: @Mic

11 Aug 2026, 12:03 UTC554 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:k 探险时间:08.11 探险目标:#赵敏儿 探险坐标:#惠州 #仲恺 探险花费:600 探险体验:服务跟课表一致。175大高个,顶级炮架。有陪洗,上床调情很认真,给我整的欲罢不能,无敌大蟒蛇🐍,主动蛇,蛇到你饱,口活一流,差点给我口出来,赶紧戴上头盔进入战斗,123结束战斗。结束后老师帮忙擦干净枪杆子,有事后萧。 探花锐评:老师比较热情,情绪价值拉满。实战利器 综合数据:#人照:7 #芳龄:24 #颜值:还够用 #身高: 175 #胸器:b 探险评级:# 乙 【甲=天菜 乙=优秀 丙=普通 丁=勉强 雷=拉垮】 联系方式:@chengjiang168 已核对相约截图

11 Aug 2026, 11:57 UTC618 viewsread 12 August 2026
Photo

#工兵探险作业报告 探险工兵:普罗米修斯 探险时间:8.11 探险目标:#糖果 探险坐标:#惠州 #港惠 探险花费:700p 探险体验:约好时间,上门,和验证无差,一个很飒的御姐,洗澡,吐槽一下卫生间,那么小,做你妈的干湿分离。不过姐姐善于聊天,善解人衣,还会一字马,传教士的时候,掰着她的腿,呈直线插,噗呲噗呲,声音好大,然后憋不住发射,洗澡走人 探花锐评:颜值很飒,奶子不大,皮肤黄皮,环境还行,就是卫生间太小了,容不下2个人,转身都难,姐姐态度很不错,累了还给按摩,肚子上有腹肌马甲线,一看就是练过的,可惜没有🐍 综合数据:#人照:和验证无差 #芳龄: 御姐 #颜值:就是一个字,飒 #身高: 163 #胸器:A 探险评级:# 乙-【甲=天菜 乙=优秀

11 Aug 2026, 11:51 UTC543 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:大飞机 探险时间:8月11日 探险目标:#糯米 探险坐标:#龙丰 探险花费:p 探险体验:我真该死,既然不转身。约好了罚站20分钟,看到这妞还行,然后聊天看到烟牙,我就想走了,秉承来了都来了精神,硬上。先洗澡,就乖乖洗了小鸡鸡。然后躺床上口,口硬了就给我戴套。重点来了,等着摸了一下肉棒,鼻子痒擦了一下鼻子,怎么感觉有股味道。我以为逼臭,然后另一只摸一下逼,闻了一下,还好沐浴露的味道。我蛇啊,69啊心情全没,然后软趴趴,一直硬不起来,再洗一下,然后继续口。还是不行,打开日本小电影,终于硬了。然后传教士进入发射。老师全程捂脸。没声音,一点情都没调。最大的一个优点,逼真的粉,真的嫩 综合数据:#人照 8分 #芳龄:17 #颜值:7分 #身高: 160cm #胸

9 Aug 2026, 08:02 UTC949 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:雷王刘华强 探险时间:8-8 探险目标:#曦曦 探险坐标:#惠州 #华贸铂金府 探险花费:600/p 探险体验: 看报告后决定cj一下,不料工兵报告也出套路了,种马有连带责任。 服务一般,就脸还行,其他的一言难尽,身材走形了都,肚子都赘肉(不是肚腩是赘肉) 探花锐评:硬件太拉胯,奶子是放完气的气球,皮肤黄皮偏黑, 建议下架, 综合数据:#人照 本人 #芳龄:26左右 #颜值:6分 #身高:165 #胸器:B 探险评级:#雷 【甲=天菜 乙=优秀 丙=普通 丁=勉强 雷=拉垮】 联系方式:@HuizhouLi88 已核对相约截图

8 Aug 2026, 22:24 UTC974 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:广漂 探险时间:8-8 探险目标:#贝贝 探险坐标:#惠州 探险花费:1200pp+100上门费 探险体验:基于某次事件后再也不去课室,叫的上门,梦初代聊(狗东西给我卖萌恶心死我了),妹子颜值跟频道神似不好评价,黄皮,不太会化妆,个子小,但是,嫩,无敌嫩,是真刚下海,紧,两个手指头进不去,胸也是够大(乳头性情时巨硬),屁股大,打起来很舒服,水多,艹起来撇撇响。 探花锐评:妹子是什么都不太懂,刚好体验了一把下海开发,什么xp都给我试了,只能说人生圆满了,综合评价:物美价廉,基于给我体验到了开发的感觉,从丙升级到丙+。 综合数据:#人照不评价 #芳龄:问就是18 #颜值:6.5 #身高:150 #胸器:B+ 探险评级:

8 Aug 2026, 22:24 UTC925 viewsread 12 August 2026

#工兵探险作业报告 工兵留名:东城 探险时间:8.8 探险目标:#丹丹 探险坐标:#惠州 #龙丰 探险花费:400(多给一块) 探险体验: 老熟人了,环境干净整洁,一次性浴巾,课表内容都有,没有因为是熟人偷工减料,态度颜值可以,耐看 探花锐评:人照6分,本人苗条,御姐 综合数据:#人照 6 #芳龄:25 #颜值:8 #身高: 160cm #胸器:b 探险等级:#乙 (甲=天菜 乙=优秀 丙=勉强 丁=拉垮】 联系方式: @aini12aa 已核对相约截图

8 Aug 2026, 11:32 UTC984 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:理塘的风 少年的心 探险时间:8月 探险目标:#雯雯 探险坐标:#麦地 探险花费:p 探险体验:在楼下等了20分钟你知道是什么感受么,我只能说热,上去后开门端详,老师样貌、颜值、轮廓与频道相似度很高(也不亏我等了20分钟了),桌子上摆放没喝完的矿泉水 化妆包,有点杂。沙发还算整洁,我是真怕喝错水啊,抽根烟随后说给我放水洗洗,上床后开始整活,口技不错没感受到什么齿感且口的时间还算有点长,有🐍 主动询问,频道上说的69和胸推我没体验到(可能我没问的原因),还有水中萧 事后帮洗,做爱上配合度可以,女上体力足,翻身抽插呈痛苦表情,身材nice 皮肤偏黄(频道是顶级美白),人照是一致的 相似度非常高,出击这么久头1次见人照一致的 颜值也蛮高,但是没出,最终还是👋搓+🐍出的。总结:雯雯老师给我

8 Aug 2026, 04:42 UTC≈1,060 viewsread 12 August 2026
Photo

#工兵探险作业报告 探险工兵:普罗米修斯 探险时间:8.8 探险目标:#神经沫 探险坐标:#惠州 #金山湖 探险花费:700p 探险体验:看了一堆好评,约了,需隔天,到了约定时间,上门,虽然有点特务接头的感觉,但是整体丝滑,进门,没有失望,不是很经验,但是绝对耐看,她只穿一件衬衫,和内裤,趴在身上画圈圈,聊着天问我吃什么,喝什么,女友感爆棚,放着轻音乐,洗澡,好仔细,耳朵,脸,全身深度清洁,上楼,ab 面按摩,吹,人弓着,胯下吹,好爽,在切面,各种调情抚摸,舔,按,戴套,女上,好强,但是女上做不出我,接着走a,传教士,后入,女上,传教士,发射,有事后萧,服务还是那么仔细。 探花锐评:颜值不是最顶的,但是服务,情绪价值,女友感真的太棒了,以后应该经常找她!ps 她的那个眼罩真的很舒服 综合

8 Aug 2026, 04:34 UTC≈1,010 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:Zzz 探险时间:8月 探险目标:神经沫 探险坐标:金山湖 探险花费:700P 探险体验: 老师很佛系,约了两三周才约到,一定要提前约。 到点见面瞄了一眼,就是我的菜赶紧交学费。人很松弛,相处没有一点紧张的感觉。 开始沐浴上课,才发现小沫皮肤又白又滑,胸又大又挺,腿又长又直,极品啊哈哈😆 转移战场服务好多,目不暇接,具体参考课表。进入战斗差点被秒了,赶紧换姿势还是很快投降。意犹未尽啊,下次再来回味。 探花锐评:软硬件都是顶级。 综合数据:#人照:9 #芳龄:21 #颜值: 9 #身高:160 #胸器:天然C 探险评级:乙+ 【甲=天菜 乙=优秀 丙=普通 丁=勉强 雷=拉垮】 联系方式:@biuoobiu 已核对相约记录

7 Aug 2026, 15:35 UTC≈1,120 viewsread 12 August 2026

#工兵探险作业报告 探险工兵:Theshy仲恺健shy 探险时间:26/08/07 探险目标:#等等 探险坐标:#惠州 #龙丰 探险花费:7 探险体验:有点吊儿痒,新菜迫不及待前往,进门灯光有点暗,老师准备了氛围灯(细节),刚开始有点尴尬不怎么说话,多聊几句开始热起来,妈蛋凑巧空调也坏了,吹风扇干活,口活应该是练过的,服务意识有待提升需要主动提出,8分硬的唧唧女上塞不进去,传教士塞了几秒才硬怼进去绑紧,小鸡吧的福音,主动拉你双手使劲揉捏奈子,越捏叫声越淫荡,123完事。 探花锐评:小麦色偏黑皮 颜值一般 穴紧 啵啵脆奈子 服务待加强 穴毛茂盛 双臂符文 综合数据:#人照:6.5 #芳龄:18 #颜值:6.2 #身高: 167 #胸器:B 探险评级:#丙

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

Posts edited after publishing

@RPzy_9 edited 2 posts 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.

First edit seen
8 August 2026
Most recent edit
12 August 2026

Citation-graph rank

Citation-graph rank — 122,609 of 1,345,403entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“惠州工兵锐评作业榜” (@RPzy_9), 4,917 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/RPzy_9.

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.