Telegram RegisterThe public register of Telegram
Telegram profile photo for 软兔测评反馈

Channel

软兔测评反馈

@RTNPCP

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

983subscribers

-532 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002682709707
TypeChannel
Username@RTNPCP
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live6 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/RTNPCP

Topic

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 18 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Growth

9831,5151,2498 August 2026 — 1,515 subscribers8 August 2026 — 1,514 subscribers10 August 2026 — 1,495 subscribers13 August 2026 — 1,488 subscribers16 August 2026 — 1,459 subscribers19 August 2026 — 1,436 subscribers23 August 2026 — 1,378 subscribers26 August 2026 — 1,353 subscribers29 August 2026 — 1,329 subscribers1 September 2026 — 1,320 subscribers6 September 2026 — 1,281 subscribers11 September 2026 — 1,226 subscribers15 September 2026 — 1,178 subscribers19 September 2026 — 1,140 subscribers29 September 2026 — 1,023 subscribers6 October 2026 — 983 subscribers8 August 20266 October 2026
16 measurements spanning 59 days, net -532. 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 903–1,595 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 02:56983-40
29 Sept 2026, 02:021,023-117
19 Sept 2026, 14:181,140-38
15 Sept 2026, 00:171,178-48
11 Sept 2026, 03:551,226-55
6 Sept 2026, 04:381,281-39
1 Sept 2026, 13:361,320-9
29 Aug 2026, 20:551,329-24
26 Aug 2026, 22:031,353-25
23 Aug 2026, 21:471,378-58
19 Aug 2026, 19:421,436-23
16 Aug 2026, 21:381,459-29
13 Aug 2026, 18:171,488-7
10 Aug 2026, 20:211,495-19
8 Aug 2026, 04:511,514-1
8 Aug 2026, 01:321,515first reading

Engagement

20 posts held, back to 30 July 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Aug 2026, 10:06 UTC541 viewsread 8 August 2026

【日期】:8.01 【美女昵称】:#水水 【联系方式】:@HZRTNP 【地区】:拱墅 【见面感觉】: 身材很好 【标签】:活泼 【身材曲线】 b 【技术含量】: 很不错 【价格】:工兵价 【年龄】:03 【身高】:160 【凶器,是否假奶】:真 【过程】:听说来了新人 本身准备第一天就来,奈何突然有事只能拖了几天,昨天一会杭州直奔软兔,到了之后妹妹已经是在房间等着我了,见面之后第一反应妹妹很开朗呀,也能看出了身材很不错,我本身比较i话比较少,妹妹见面很主动便抱了上来,然后便开始和我聊天,很好不会冷场,还会主动亲亲。嘴巴也是很软很甜啊,提出的要求也是基本都可以满足的,但是我出差两天没咋睡觉太累了就没要妹妹给释放,但是抱着聊聊天也是很可以了。是个好妹妹。

2 Aug 2026, 07:07 UTC636 viewsread 8 August 2026

【日期】:8.1 【美女昵称】:#涵涵 【联系方式】:@HZRTNP 【地区】:拱墅 【见面感觉】:挺好的 【标签】:可甜可御 【身材曲线】:挺好 【技术含量】:还行 【价格】:600 【年龄】:19 【身高】:165 【凶器,是否假奶】:否 【过程】:群里看见有新人,看见建模看着不错,就出击了,进房看见妹子比照片还好看,属于校花级别的,瞬间感觉赚大了,妹子很贴心的帮忙拿水跟漱口水,态度很好,聊了十分钟很开心,破冰后忍不住就吻上了,妹妹还是挺主动的,是个小蟒蛇,吻的时候嘴巴很甜很软,妹妹皮肤也比光滑的,胸正好一手掌握,让人沉溺其中,整体还是挺配合的,让人爱不释手,沉迷其中,情到深入脱去上衣,独留一甲,身材真的很不错,腿很长,喜欢,小兄弟早就对着敬礼,因为新人打飞机还不是很熟练,这个能理解,最后在妹妹娇喘抚摸下,自己顺利释放,满足感油然而生,事后点上一根烟,享受最后的温存,有机会还会再来的。

1 Aug 2026, 09:35 UTC601 viewsread 8 August 2026

【日期】:8月#软兔女仆 【美女昵称】:#涵涵 【联系方式】:@HZRTNP 【出击人】#王牌试钟员 【地区】:拱墅 【见面感觉】:素人嫩妹 【标签】:#冷白皮 #素人嫩妹 【身材曲线】完美 【技术含量】:学习中 【价格】:测评价 【年龄】:19 【身高】:163 【凶器,是否假奶】:B 【过程】: 客服私信我说有素人新人嫩妹,给了新人优惠测评价,果断出击看看,驱车前往,第一眼见到确实嫩,白。 进入房间开始操作,嫩妹确实不一样,充满了素人气息,穿了一个透明的睡衣,摸起来手感很好,胸B,但是很软,葡萄很小。 新人小蟒蛇,身材好,皮肤白,光滑平坦,非常配合,让干嘛就干嘛,新人留一甲,可以隔裤操作。 最后在指导下慢慢出货。妹妹说湖北刚来的杭州没几天。 新人素人,喜欢冷白皮嫩妹的可以冲。 缺点的话主动性差一点,不过新人素人也可以理解,其他的都很听话配合。

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

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.

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

“软兔测评反馈” (@RTNPCP), 983 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/RTNPCP.

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.