Channel
@jiuyigongguanrib
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
468subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003434880072 |
|---|---|
| Type | Channel |
| Username | @jiuyigongguanrib |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/jiuyigongguanrib |
Adult — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 17 Sept 2026, 19:37 | 468 | +5 |
| 8 Sept 2026, 15:58 | 463 | -3 |
| 30 Aug 2026, 03:05 | 466 | -2 |
| 22 Aug 2026, 11:07 | 468 | +2 |
| 14 Aug 2026, 13:58 | 466 | -2 |
| 7 Aug 2026, 06:56 | 468 | no change |
| 7 Aug 2026, 05:32 | 468 | first reading |
20 posts held, back to 28 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#诗雨 【联系方式】：@shiyu2027 【验证留名】：GatorPie 【验证时间】：8月6日 【修车水费】： 【流程小文】： 诗雨妹妹，人照9分，颜值如何看频道照片就知道了，苗条型身材，属于近期探到的很不错的宝藏嫩妹。 在非聚集高层小区开课，课室宽敞豪华，妹妹自聊也很注意安全让人放心。 进门眼前一亮，颜值属于走在马路上也颇有回头率的那种，聊了几句脱衣去yyy，身上肤色不白且有大片符文有点可惜，不然就是极品硬件嫩妹了。不过有一说一大花背纹得不难看，老汉推车时老汉我一直在后面欣赏蛮带感。 和略精神的外在不同诗雨妹妹的服务态度却非常认真和乖巧，会问你水烫不烫枕头是否舒服。做爱的反馈也是很自然，cjs一边看着美颜在身下微皱眉呻吟一边输出真是太享受了。 整体在这个价位上蛮能打。有点遗憾妹子前两天嘴唇被蜜蜂蜇了有点肿，无法享受妹子的…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#格格 【联系方式】：@liyang1233 【验证留名】：Mi Ke 【验证时间】：8月x日 【修车水费】：工兵p 【流程小文】：重逢总是带着些许期待，第七次来找格格老师，尤其这是搬家后的第一次碰面。格格老师还是那个格格老师，肌肉线条像雕塑般利落，身体里却藏着惊人的爆发力。 她的口技依然是一绝，那些细腻的声浪和气流，总能轻而易举地把人推向微醺的边缘。而当真正进入正题，女上位与传教士的切换被她演绎得像是一场行云流水的全自动体验，一字马更是将身体的张力拉满。这绝不是单方面的碾压，而是势均力敌的交锋，你来我往间，我竟有种重回纯粹角力场的错觉。 最让我暗自惊叹的，是她身体比例的微妙重塑。原本偏扁平的臀部，如今竟出落得肉感十足，还带着利落的翘度。她笑着透露自己长了六斤肉，我不禁在心里感叹：这分量添得真是恰到好处，多一分则腻，少一分则寡。 …
沪杭91公馆报告 https://t.me/jiuyigongguann 【妹子花名】：#小鱼 【联系方式】：@xiaoyu8576 【验证留名】：大智若愚 【验证时间】：8月4日 【修车水费】：竞拍p 【服务内容】：有的打✅ ① 陪浴 ✅ ② 舌吻 ✅ ③ 69舔逼 ✅ ④ 情绪价值✅ ⑤ 毒龙 各项指标因人而异，请尽量客观填写： 【人照相似】：人照相似度高，颜值高女仆出生 【身材皮肤】：身高158，皮肤手感Q弹，白皮 【凶器罩杯】：胸型A，乳头颜色浅 【户型湿紧】：户型颜色浅色，人工白虎，水量多紧度中上 【课室环境】：停车好停方便 【个人卫生】：不抽烟，有浴巾，事前事后一起清洗，洗的很仔细 【时间管理】：开课准时，排课宽松，课时做完 【服务总结】：课表服务完整，服务到位，过程不机车 【流程小文】： #前言 感谢91公馆给我这个机会，让我有机会挑战小鱼老师，很久没有约满姐了，…
【妹子花名】：#月月 【联系方式】：@yydaxiaojie 【验证留名】：金枪小帅 【验证时间】：8月4日 【修车水费】：工兵500p 【流程小文】：提前一天预约，第二天还是在楼下罚站了一小时，妹子去拍写真去了，本来想发火的，不过看到真人，是个年轻妹子，刚来杭州，玩心重也不好说什么，妹妹是个瘦小的重庆嫩妹，人照相符，性格比较沉默，胸小，毛少，挺紧的，不催，各种姿势都能满足，喜欢萝莉的可以去。
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#诗雨 【联系方式】：@shiyu2027 【验证留名】：nick 【验证时间】：8月3日 【修车水费】：600p（工兵5折） 【服务内容】：有的打✅ ① 陪浴✅ ② 舌吻✅ ③ 69舔逼 （我不喜没要） ④ 情绪价值✅ ⑤ 毒龙 各项指标因人而异，请尽量客观填写： 【人照相似】：人照9分 【身材皮肤】：165，90,黄黑皮，皮肤光滑 【凶器罩杯】：b 【户型湿紧】：穴水润紧 【课室环境】：高层小区，安全性高，装修干净整洁 【个人卫生】：抽烟（我不介意），事前事后有清洗 【时间管理】：开课准时，排课宽松 【服务总结】：服务态度很好，无机车行为 可以不写，不影响积分获得，工兵，竞拍等活动必写： 【流程小文】： 提前2天约的老师，课室在市区高层小区私密性要比老小区好不少，到了楼下…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#芭比 【联系方式】：@babia4 【验证留名】：Jay 【验证时间】：8月X日 【修车水费】：1200 【流程小文】： 又见工兵，也是好久没有工兵了，谢谢小戏和91，照例总结一些有价值信息，尽量客观，但是你最好别参考太多。 1.小区很熟了，总体体感还是安全的，课室卫生中規中矩吧 2.妹妹家居服见客，颜值在线，人照不错，妆容也可以，略卡粉 3.外向广东嫩妹，无须刻意破冰，挺主动也可爱的 4.培育洗的AB都有，没有花活，洗的蛮认真的 5.165左右的身高，正常黄皮，微梨的屁股在后入时有一定的视觉冲击，皮肤状态尚可吧，小小玉足一枚 6.没错的，打卡继续姐，聊起来还赋予继续两个字之人生的意义 7.相对嫩妹，A面服务有点东西，鼻吸的挺认真的，口活也可以，话语间妹妹对自己的口活应该是蛮有信心的 8.进入后紧度润度都可以，反馈真实，嘴硬…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#bb 【联系方式】：@bbxx152 【验证留名】：Steven 【验证时间】：8月3日 【修车水费】：1500p 【流程小文】：广深来的老师服务确实是到位！提前半小时提醒点外卖准备喝的。频道非本人不过本人也很漂亮，脸好小。 沙发休息了会进入全自动洗刷刷，胸大概C手感很好皮肤贼好贼光滑，右后肩有个小小的纹身，据说是海鸥，下面是英文名一长条，看不清那就必然就是Steven无疑了，🐔冻。老师很细致，前面洗完洗后面，前面磨磨后面磨磨，妙妙不可言！一边水中萧一边媚眼如丝地看着你，居高临下看脸更小精致了还好我有阿弥陀佛大法，坚持不到床上可太丢人了。 洗完老师换好qqny，光顾着看腿了，小脚加黑丝美腿美滋滋，口活花样贼多，吸吸舔舔快速吞吐真是让人欲罢不能。女上起手老师抓着手不放，边动边挨个舔吸手指主动抓着让你掐脖子，抖抖抖抖抖MⓂ️。女上顶…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#BB 【联系方式】：@bbxx152 【验证留名】：M 【验证时间】：8月3日 【修车水费】：1500p（-200优惠） 【流程小文】： 总体评价：超级好评，纳入复刷名单 初见： 提前2天约的宝宝，周末就开始闲聊预热了，宝宝真的无敌好，很健谈，深夜emo的时候还给我唱歌听。期盼了2天终于见到宝宝真人。房间里放着歌，像下班回家的感觉。因为有了前两天的预热。跟宝宝感觉不是初识，像女友，又像邻家姐姐。 宝宝穿着一身包臀长裙，漂亮，没有do过的痕迹，是我喜欢的标准瓜子脸。身材比例极佳，前凸后翘，穿着长裙都能看得出的细腰长腿。引我入座后搂住纤腰，腰侧柔弱无骨，环保过去摸到了心仪的马甲线（我可太爱马甲线了）。宝宝说“后面不急吧，我喜欢慢慢来” 我可太爱慢慢来了（非常讨厌sop）。我们在沙发上聊天、拥抱、拥吻，亲琢到挑逗开宝宝的小嘴热吻。…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#芭比 【联系方式】：@babia4 【验证留名】：吾劳工 【验证时间】：8月2日 【修车水费】：工 【流程小文】： 硬件：身材不错，高挑，享受这个感觉，脸很好看 周日劳工出奇的去日比，这个真的是因为芭比的魅力所致，非常的不错，感受到了嫩妹给劳工出击路上提供了多大的动力。和老师约好后，因为离的有点远，加上双休出游的家庭多，一路又开了毛50分钟。遥控上楼后，来到老师的课室，微开的门，老师站在旁边，真的热情！让我感受到了南方姑娘热情。一起闲聊了一会儿后，和芭比一起洗澡，芭比给我洗的很认真，看着芭比的长相，确实好看，让我想到了某故人，确实有部分神似。和芭比来到创伤后，没想到还挺主动的，一顿大舌吻，本来劳工一般的不舌吻的，但是看到芭比这么的主动，内心哪里还忍得住。69因为劳工确实不喜欢就没要，用身体最大的器官感受着芭比B的形状。戴套进入的…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#温软软 【联系方式】：@wenrunr 【验证留名】：可口可乐 【验证时间】：8月2日 【修车水费】：x00P 人照：人照10成（照片6.6号视频） 头发盘起来的（有点淡淡的香味）精致妆容勾勒出知性的轮廓 邻家大姐姐感 大哥的女人既视感（现实十个有九个行注目礼） 身材：170左右 进门一身红裙风情万种（要求碎花奈何没有，红裙也是别有一番风味）前凸后翘 别样美感 屁股饱满诱人有肉 摸起来非常舒服 罩杯：E杯 挺拔有弹性 摸起来软软糯糯 一只手抓不完 真的很大！乳头小小一个，舔起来舌感很舒服喔 户型：小馒头 人工白虎 粉嫩紧润 环境：小区房 路边大把停车位 课室干净整洁，看得出都有很认真在打扫 流程小文： “阳光明媚啊，适合出击~” 温软软早有耳闻，学生会独家，朋友也是有推荐过。准备约时间奈何回消息有点慢（后面了解…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#温软软 【联系方式】：@wenrunr 【验证留名】：@hzoldking 【验证时间】：8月1日 【修车水费】：1200p 【流程小文】： 关注了温软软老师蛮久，好多兄弟好评为颜值御姐。找到机会约课前往一探，位置在东站附近某新小区，环境好进出入少，无门禁。 一睹芳容后，仔细端详老师，和频道照片视频基本一致，一身白色连衣裙，妆容精致又不失气质，一双大长腿白花花诱人，和自己预期完全符合。进门后老师热情迎接，一个大大的拥抱后主动送来香吻，有点猝不及防。在沙发上寒暄时，温老师主动拉着我的手感受老师的肉体，边舌吻边诱惑，热情而主动，不愧是妖媚女王。情绪价值这块从进门开始就拉满了。 小弟弟被撩到躁动不安，温老师也感受到我内心的饥渴，适时提出鸳鸯浴。洗浴过程全程自动，用全身帮忙涂沐浴露，正如老师名字一样，温老师身体软软的很舒服，浴室play…
沪杭91公馆报告 https://t.me/jiuyigongguann 必填项： 【妹子花名】：#Yuki 【联系方式】：@yuki89900 【验证留名】：骏歌 【验证时间】：7月30日 【修车水费】：1500P（优惠券） 【流程小文】：听闻南方名师到杭，怎能错过绝佳机会。 身高168，无纹身，全身通体雪白，1.5号色，胸C，小蝴蝶，人工白虎，颜值高。 今日穿搭是短T恤+牛仔短裤，进门递水交水费聊坐沙发，在这个环节就约定好结束送老师去机场，Yuki也是当天下午临时起意要出去旅游。 洗浴环节也是全程帮洗，依旧残废骏上线，前后洗的很仔细，紧接着蹲下含水口衔鸡吧开始水中萧，小青龙在Yuki的嘴里慢慢变长、变大，两个回合下来已经勃起很狂野的状态了… 来到房间，我让Yuki侧躺在我旁边，很像女友的感觉，抱起她的脸开始接吻，Yuki的舌头很软、很舒服，随即我开始在Yuki身上游走…舔脖子、锁骨、到胸这里停下，一把…
Showing the 12 most recent of 20 posts we hold for @jiuyigongguanrib. 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.
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.
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.
@jiuyigongguanrib named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“（杭州-上海）91公馆日报” (@jiuyigongguanrib), 468 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/jiuyigongguanrib.
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.