Channel
@maomaobaoyangx
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
439subscribers
+15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003283539252 |
|---|---|
| Type | Channel |
| Username | @maomaobaoyangx |
| Created | Between 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/maomaobaoyangx |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 |
|---|---|---|
| 14 Sept 2026, 04:17 | 439 | +2 |
| 6 Sept 2026, 10:00 | 437 | +14 |
| 29 Aug 2026, 14:28 | 423 | -1 |
| 23 Aug 2026, 06:55 | 424 | -1 |
| 15 Aug 2026, 01:18 | 425 | +1 |
| 8 Aug 2026, 05:30 | 424 | no change |
| 7 Aug 2026, 18:07 | 424 | first reading |
16 posts held, back to 8 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
编号EL1043 省份:四川 城市:成都 年龄:23 身高:165 体重:90 罩杯:B 雪历:大专 职业:舞蹈 是否是chu女:否 可不可以口:否 能不能内射；否 能不能无套:否 能不能SM:否 能不能外省:看情况可 有没有纹身:无 是否可以过夜:可 可不可以同居:否 月可陪伴天数:8，短期3天 大概姨妈日期:十几号 找金主的原因:存钱 月生活费多少:2W，短期3/8k 分几次给生活费:2 自我介绍加分项:跳舞/有反差/听话 对老板雷点:不爱干净没素质情绪不稳定 介绍费:7888🐱cz
视频收录成功！ 编号：260808355716
收录成功！ 编号：260808355716
视频收录成功！ 编号：260808187825
收录成功！ 编号：260808187825
视频收录成功！ 编号：260808728775
收录成功！ 编号：260808728775
❌ 重复投稿 168 小时内已提交过高度相似资料
❌ 重复投稿 168 小时内已提交过高度相似资料 编号：2608051561
❌ 重复投稿 168 小时内已提交过高度相似资料 编号：2608020363
❌ 重复投稿 168 小时内已提交过高度相似资料 编号：2608051615
❌ 重复投稿 168 小时内已提交过高度相似资料 编号：2608020246
Showing the 12 most recent of 16 posts we hold for @maomaobaoyangx. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“猫猫🐱工作室” (@maomaobaoyangx), 439 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/maomaobaoyangx.
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.