Telegram RegisterThe public register of Telegram
Telegram profile photo for 雨宝の饭搭子(成都版)

Channel

雨宝の饭搭子(成都版)

@yubaogugude999

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

12,362subscribers

+3,887 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003761488147
TypeChannel
Username@yubaogugude999
Description积极开课~喜欢素质饭搭子🥰 私聊 @xhhdqq 群组 https://t.me/acmfdxb 双向联系 @YubaoCHT_bot
CreatedBetween 1 February 2026 and 16 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 November 2026
Measurements held42
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/yubaogugude999

Topic

Personal blog — 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 51% 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 the other topics.

Growth

8,47512,38710,4318 August 2026 — 8,475 subscribers8 August 2026 — 8,475 subscribers9 August 2026 — 8,546 subscribers12 August 2026 — 8,653 subscribers16 August 2026 — 8,747 subscribers18 August 2026 — 8,768 subscribers21 August 2026 — 8,798 subscribers24 August 2026 — 8,831 subscribers27 August 2026 — 8,863 subscribers30 August 2026 — 8,911 subscribers1 September 2026 — 8,937 subscribers6 September 2026 — 9,016 subscribers10 September 2026 — 9,030 subscribers14 September 2026 — 9,049 subscribers18 September 2026 — 9,093 subscribers27 September 2026 — 9,135 subscribers5 October 2026 — 10,345 subscribers9 October 2026 — 11,478 subscribers13 October 2026 — 12,387 subscribers14 October 2026 — 12,344 subscribers16 October 2026 — 12,302 subscribers17 October 2026 — 12,266 subscribers17 October 2026 — 12,237 subscribers18 October 2026 — 12,240 subscribers19 October 2026 — 12,243 subscribers20 October 2026 — 12,245 subscribers22 October 2026 — 12,264 subscribers23 October 2026 — 12,265 subscribers24 October 2026 — 12,277 subscribers25 October 2026 — 12,288 subscribers26 October 2026 — 12,296 subscribers27 October 2026 — 12,294 subscribers29 October 2026 — 12,299 subscribers30 October 2026 — 12,290 subscribers31 October 2026 — 12,287 subscribers31 October 2026 — 12,299 subscribers1 November 2026 — 12,308 subscribers2 November 2026 — 12,345 subscribers3 November 2026 — 12,352 subscribers4 November 2026 — 12,354 subscribers6 November 2026 — 12,367 subscribers7 November 2026 — 12,362 subscribers12,3628 August 20267 November 2026
42 measurements spanning 91 days, net +3,887. 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 7,888–12,974 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
7 Nov 2026, 01:4112,362-5
6 Nov 2026, 00:0112,367+13
4 Nov 2026, 21:2012,354+2
3 Nov 2026, 21:4612,352+7
2 Nov 2026, 21:5612,345+37
1 Nov 2026, 18:3812,308+9
31 Oct 2026, 21:5512,299+12
31 Oct 2026, 00:2812,287-3
30 Oct 2026, 02:5712,290-9
29 Oct 2026, 00:5012,299+5
27 Oct 2026, 22:1912,294-2
26 Oct 2026, 20:3612,296+8
25 Oct 2026, 22:3512,288+11
24 Oct 2026, 00:4512,277+12
23 Oct 2026, 02:5912,265+1
22 Oct 2026, 03:1512,264+19
20 Oct 2026, 20:0012,245+2
19 Oct 2026, 18:2112,243+3
18 Oct 2026, 19:1912,240+3
17 Oct 2026, 22:2712,237first reading

Engagement

42 posts held, back to 16 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 37 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
40.9%
avg views ÷ 12,362 subscribers
Avg views / post
5,050
15 posts measured
Reaction rate
0.145%
reactions ÷ views · ER floor
Posts in window
15
of 42 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 14 of 15 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 7 November 2026
Posts held42 (16 July 2026 – 7 November 2026)
Views total75,821
Reactions total109
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 20:38 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

Photos
52
Videos
15
Links
5

Lifetime counters from Telegram’s own channel header, read 7 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 52s
Average length
16s

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

265 reactions across 40 posts, in 14 distinct kinds. The most used accounts for 79.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤21079.2%
🥰186.79%
🫡93.40%
👍62.26%
😁62.26%
😭62.26%
❤‍🔥31.13%
🎃10.377%
🐳10.377%
😐10.377%
😢10.377%
🤨10.377%
🤩10.377%
🤬10.377%

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 40 of the 42 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 265 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 42 most recent posts we hold, published 16 July 2026 to 7 November 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 42 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yubaogugude999. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 42 most recent posts we hold for this entry, published 16 July 2026 to 7 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 15 posts held from the last 30 days (13.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 14:20 UTC817 views1 reactionsread 7 November 2026
Photo

#成都 #武侯 #雨宝 #满分女友 @xhhdqq 人照:10 颜值:10 身材:10 162 a+胸 排骨 服务:10 环境:10 简述:第一个满分女友!!不枉我苦苦约了大半年,居然真的约到了雨宝休息后的首课。 真人比我想象中的瘦多了,后来一问是之前减了30斤,从萌妹变成甜系御姐了,嘟嘟脸变成了瓜子脸,感觉像抖音博主奈奈美。 坐下雨宝先嘘寒问暖了一波,捧着我的手帮我搓搓,被成都降温的我瞬间暖和了起来。中午没吃饭赶过来,雨宝还帮我准备了奶茶和小零食,一口喝着饮料一口吃着被投喂的零食。洗浴也是全程几乎不用我动手,出浴室帮我浑身擦干净。 躺到床上雨宝就直接舌吻上来了,也可以说是霸道的索吻,雨宝的舌尖很小,像她的下巴一样。舌不够一直舌,像被抽干了脑髓,陷入了温柔乡。雨宝口技也很棒,值得一提的是一开始会先舔蛋蛋,很酥很麻。雨宝下面清理的特别特别干净,没有一点毛扎,可惜没有69了,真想大舔特舔。 正戏女上开始,不亏是刚休息结束的,又紧又…

❤1

7 Nov 2026, 14:20 UTC812 views1 reactionsread 7 November 2026

老师ID:雨宝 @xhhdqq 出击时间:11.7 报告发表:彼岸(玉玉版) 报告评价:久闻雨宝大名,也是约上一课,花魁名不虚传,见面一看哇!今天是AV女优妆雨宝😁打扮好像,全程真是情绪价值拉满给我搞害羞了,真没想到细糠这么细,整个课程话都没停过,本来话多的我压不住雨宝当场变成萌新时期整不会了少有腼腆的我。教室有小冰水饮料,有零食,洗澡全自动享受就行啦,大蟒蛇管够,口活顶级口的时候舌头乱动安逸🥹身材小小的尤其腰感觉一只手长度下面干净白虎进去有包裹感做的时候也主动要亲亲,口活真是太好了。聊的忘时间了差点超时匆匆忙忙穿衣最后拥抱离开。羡慕成都ly,这个情绪价值的雨宝。

❤1

7 Nov 2026, 14:19 UTC832 viewsread 7 November 2026
Photo

8号排完啦宝宝们🥰 雨宝怕被桩伤,所以一天一天在慢慢的排课,没有回复到的宝宝不要着急😣!求理解!🥰 私信有点杂乱,有的宝宝可能没回到私信(日式91度鞠躬🙇‍♀️)🥰 雨宝不收定金,任何见面前的任何收费都不要信!小心被骗! 唯一账号: @xhhdqq ☝️双向账号联系 :@YubaoCHT_bot (排课信息排完后就会删除🫶)

6 Nov 2026, 10:30 UTC≈1,940 views1 reactionsread 7 November 2026
Photo

7号排完啦宝宝们🥰 雨宝怕被桩伤,所以一天一天在慢慢的排课,没有回复到的宝宝不要着急😣!求理解!🥰 私信有点杂乱,有的宝宝可能没回到私信(日式91度鞠躬🙇‍♀️)🥰 雨宝不收定金,任何见面前的任何收费都不要信!小心被骗! 唯一账号: @xhhdqq ☝️双向账号联系 :@YubaoCHT_bot (排课信息排完后就会删除🫶)

🤬1

31 Oct 2026, 06:16 UTC≈5,530 views7 reactionsread 7 November 2026
Video

【妹子花名】:雨宝(咕咕) 【妹子账号】:@xhhdqq 【验证留名】:轩轩 【验证时间】:10月 【所在位置】:武侯区 【修车水费】:5200(8hcos) 【身高身材】:160 左右 【妹子年龄】:永远18 【凶器罩杯】:a 【服务内容】:口洗做,陪我拍照集邮 【推荐程度】:9.5分/满分10分 【个人发挥】:也是终于见到咕咕啦!而且我还约到了cos版!约到后,咕咕仔细询问我喜欢的角色,主题是万圣节🎃,那当然得是我最爱的雷姆(万圣节版),咕咕也问了我是需要她提供服装还是我自己来提供,反正我觉得我买了也穿不了就让咕咕准备,所以水费就包含了8小时的费用➕cos服➕假发➕妆容而且咕咕自带教室一共5200,我只用洗个吊出门。 按照指令上楼,开门后先是看到女巫帽的尖尖,顺视往下看到一双(一只) 忽闪忽闪的眼睛,嘴也笑着说“昴君,欢迎回来——”啊啊啊啊啊! 坐下后我的今日专属“雷姆”咕就主动贴上来,此刻电视里放着音乐,可是我已经听不进去…

❤7

20 Oct 2026, 07:21 UTC≈9,040 views12 reactionsread 7 November 2026

休息了🥹 休息到11月初🥺

🫡7😭3❤1😢1

20 Oct 2026, 05:27 UTC≈8,720 views9 reactionsread 7 November 2026

👧艺名: #雨宝 🤖课表: https://t.me/yubaogugude999/101 📒小作文: 📌 基本信息 出击时间:2026年10月19日 留名:Nefelibata(漫步云端) 修车费用:600p 🧍‍♀️芳龄:20 ⛳位置: 武侯高升桥 ⭐️ 综合评分 🌧️ の颜值:雨宝瓜子脸,脸很小。妆容也很精致,眼睛忽扇忽扇的很大,看着你的时候,诱惑拉满。清纯反差风,越清纯越勾人,简直直击灵魂。 🌧️ の身材:160/75的样子,白皮肤,人工白虎一线天,胸部B。配着这么娇小的身材,刚好够用。 🌧️ の态度:给的情绪价值特别高,满满的陪了80分钟,一点也不催,出击以来态度最好的老师。 🌧️ の环境: 属于酒店公寓吧。有一次性浴巾,桌子上还有小零食,还给准备了奶茶,细节感拉满。 🌧️ の服务:课表有的基本上都会做,大蟒蛇,还可以满足一些其他小要求。 📝 出击の过程: 第一次约雨宝,没想到就约上了。感觉自己…

❤9

18 Oct 2026, 06:12 UTC≈5,770 views14 reactionsread 7 November 2026
Forwarded from @tudoudefenxiangPhoto

🥔❤️洋芋宝宝 【宝宝花名】:#雨宝 【宝宝车牌】:@xhhdqq 【洋芋留名】:#小土豆 【所在位置】:成都 【修车水费】:6p 10pp 更多看频道课表 【是否代聊】:自聊 【打上花火】:#嫩妹车 #小蛋糕 #大蟒蛇 #法式香吻 #情绪价值 #女友感 #小小只 #香香 #软软 #可爱 🥔❤️综合品鉴 【优点】:进门饱饱,亲亲脸蛋,亲亲嘴巴,亲亲舌头,贴贴宝宝,贴贴脸蛋,贴贴嘴巴,贴贴~冻住不许走,被黏住了,进门的时候,房间门反锁了,雨姐在咯咯格坏笑🤗,丸辣!!! 【性价比】: 9.9分/满分10.0分 【推荐程度】:9.9分/满分10.0分 🥔❤️品尝洋芋 下雨天炖土豆——(就不告诉你) “终于见到土豆妹妹了”“雨啵窝心里苦,不过在开始之前窝要考泥一下😈“ ”窝们的暗号是——下雨天炖土豆→()“”啊,哇哇,不会吧,还有第二关??“ …

❤10😁2😐1😭1

18 Oct 2026, 04:36 UTC≈4,010 views1 reactionsread 7 November 2026
Photo

🥳成都外围🥳全国包养🥳全国外围 🥳成都外围 全成都最靠谱最真实的外围资源 质量严选,优惠活动最多 带给您最好最优惠的外围体验。 外围频道: @gougedh_bot 反馈频道: t.me/chengduwaiweibaogao 🥳全国包养 https://t.me/paidaxingby 入会享6折,7888仅需4800,6888仅需4200,不满意可退可换,支持担保平台 🥳全国外围 https://t.me/gougequanguoww

❤1

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

@yubaogugude999 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.

First edit seen
24 August 2026
Most recent edit
26 August 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @yubaogugude999 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
18 August 2026
Most recent seen missing
6 November 2026
Median time before seen missing
7 days
Seen missing in the last 30 days
1

Forward network

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

“雨宝の饭搭子(成都版)” (@yubaogugude999), 12,362 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/yubaogugude999.

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.