省份:湖南 城市:益阳 年龄:20 身高:160 体重:89 罩杯:B 职业或雪生:❄️生 是否是chu女:否 可不可以口:能 是否可无套:否 是否可内🐍:否 是否可SM:能 有没有纹身和抽烟:否 是否能去周边城市:可 是否能去外省:可 是否可过夜:可 是否可同居:否 大概姨妈日期:月中 月可陪伴天数:2-3天 (长期可谈) 月生活费要多少:2天4k 3天6k 分几次给生活费:2次 DF自我介绍加分项:温柔体贴脾气好,长相清纯,听话配合不事多,身材好,说话温柔声音甜,会唱歌会跳舞,有舞蹈功底柔韧性好,五官精致,全身无整,妈生脸,可甜可盐可御姐,可素颜见 无压力 刚接触,圈子干净,没有不良嗜好,是个小m,有情绪价值。 对金主的雷点(不接受):暴力 介绍费:7888 dsz

Channel
甜甜国际苞养
@tutubaobei06
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,344subscribers
+2 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002185987283 |
|---|---|
| Type | Channel |
| Username | @tutubaobei06 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/tutubaobei06 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 22:22 | 1,344 | +1 |
| 28 Aug 2026, 01:03 | 1,343 | +5 |
| 24 Aug 2026, 14:48 | 1,338 | -8 |
| 20 Aug 2026, 19:02 | 1,346 | +3 |
| 15 Aug 2026, 02:27 | 1,343 | +1 |
| 14 Aug 2026, 08:00 | 1,342 | no change |
| 14 Aug 2026, 07:48 | 1,342 | first reading |
Engagement
5 posts held, back to 12 August 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.
- ERR · 30 days
- 4.79%
- avg views ÷ 1,344 subscribers
- Avg views / post
- 64.4
- 5 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 5 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 1 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 5 (12 August 2026 – 12 August 2026) |
| Views total | 322 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 08:00 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
省份:北京 城市:北京 年龄:20 身高:168 体重:56kg 罩杯:36D 学历:大专 职业:自媒体 是否chu女:不是 能否接受SM:否 能否接受口:可以 能否接受(体检后)无套:否(怕怀孕) 能否接受内设: 否 可否同居:否 可否过夜:可以 月可陪伴天数:3天(长期可谈) 可否飞往外地:可(近一点可以) 最快多久出发:提前沟通 是否有港澳通行证:否 是否有抽烟和纹身:否 vv雷点(不接受男友的):油腻、地中海,抠门 大姨妈啥时候来:月底 生活费要多少:9k (生活费是否可以分次):可 自我加分项(认真填写自己信息):本人是个活波开朗的女子 长相清纯 可爱 情商高 不做作 肤白貌美 身材高挑 气质出众 身材比例好 个人天赋,🛏️上反差 高潮时💦多 会玩,放得开 天然🐻大 屁股大 情绪价值拉满 介绍费:7888 dsz
省份:广东 城市: 深圳 广州 年龄: 20 身高:163 体重:47 罩杯: b 职业: 刚毕业 是否是chu女:no 可不可以口: yes 能不能无套(体检/试纸后): no 能不能内社: no sm能不能:no 有没有身上画画(纹身): no 是否可外地: 周边可 是否可过夜:yes 可不可以同居: no 月可陪伴天数:2天(相处合适可谈长期) 大概姨妈日期:25 不能接受的雷点: 脾气不好 月生活费多少: 5k 分几次给生活费: 1次 自我介绍加分项: 本科高校刚毕业,性格温柔体贴 很听话 长相甜美清纯 皮肤白嫩 生活圈子小 爱干净 没有不良爱好 与人为善 懂礼仪谈吐文雅有素质 介绍费: 7888 三国 吕布
省份:陕西 城市:西安 郑州 年龄:20 身高:177 体重:73kg 罩杯:85F 工作还是雪生:刚毕业 雷点(不能接受男友的):过于肥胖,脾气暴不尊重对方 是否chu女:不是 能否接受SM:可以接受一点点 是否能接受口: 行 能否接受无套:不行 可否接受内设:不行 可同居:行 可过夜:行 月可陪伴天数:3天(相chu合适可谈长期) 可否其他城市:行 最快多久出发:提前说 大姨妈啥时候来:26 生活费要多少:3天6k (生活费短期2次 长期3-4次能否接受):1-2 自我加分项:微胖大胸身材,天然的F罩杯 性格很好开朗活泼,温柔体贴 可接受喜好穿丝袜制服,配合度很高 腿长 很听话 情绪价值到位 介绍费: 6888 三国 吕布
省份:江苏 城市: 苏州 无锡 年龄:21 身高:163 体重: 106 罩杯:D 职业:自媒体 是否chu女: 否 是否能口:能 是否能SM:轻轻微 是否能无t(体检或测纸):能 是否能内she :不能 是否能同居:能 是否能过夜:能 月可陪伴天数:3天(合适可谈长期) 最快出发时间:协商 大姨妈几号来:月中 可否飞其他城市:能 是否抽烟或纹身:有 不能接受的雷点:不卫生 生活费需要多少:7.5k (生活费接受分几次给):2 自我加分项(优点/强项):平时与人为善 真诚懂事 温柔体贴 🐻大纯天然 腰臀比很赞 敏感水多 很乖很听话 配合度💯 介绍费:7888 三国 吕布
Showing the 5 most recent of 5 posts we hold for @tutubaobei06. 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 — 1,253,346 of 1,629,362 entries 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 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“甜甜国际苞养” (@tutubaobei06), 1,344 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/tutubaobei06.
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.