📌 标题:品尝姐姐的母乳 👤 投稿者:云烟 洛 (🌟 萌新上路) 📦 资源详情:视频 4 个 📝 简介:我原本胸到B罩杯,感觉有点小,所以买了一点空运催乳剂打上,结果。这个药物的功效在我身上起到了翻倍的效果,从此以后,我就成了一头每天都要产出母乳的奶牛 🔗 进入精品频道 💬 评论区获取资源
👍3🤣1🥰1
Signed 成人大学投稿机器人2

Channel
@o_t_e_x
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
111,822subscribers
+22,977 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002787635721 |
|---|---|
| Type | Channel |
| Usernames | @chengrendaxuegongchuang @o_t_e_x |
| Description | 内容都在评论区 商务合作 @Biedongfeifeidexinbot |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 130 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/o_t_e_x |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 15:47 | 111,822 | +17 |
| 17 Nov 2026, 14:31 | 111,805 | +427 |
| 14 Nov 2026, 12:49 | 111,378 | +7 |
| 14 Nov 2026, 11:17 | 111,371 | +406 |
| 11 Nov 2026, 15:38 | 110,965 | +31 |
| 11 Nov 2026, 12:09 | 110,934 | +257 |
| 9 Nov 2026, 20:54 | 110,677 | +31 |
| 9 Nov 2026, 17:31 | 110,646 | +232 |
| 8 Nov 2026, 10:47 | 110,414 | -1 |
| 8 Nov 2026, 10:08 | 110,415 | +214 |
| 7 Nov 2026, 06:36 | 110,201 | +9 |
| 7 Nov 2026, 06:09 | 110,192 | +202 |
| 6 Nov 2026, 08:40 | 109,990 | +32 |
| 6 Nov 2026, 05:48 | 109,958 | +217 |
| 5 Nov 2026, 09:07 | 109,741 | +63 |
| 5 Nov 2026, 03:01 | 109,678 | +199 |
| 4 Nov 2026, 07:26 | 109,479 | +12 |
| 4 Nov 2026, 05:00 | 109,467 | +127 |
| 3 Nov 2026, 06:19 | 109,340 | +13 |
| 3 Nov 2026, 05:17 | 109,327 | first reading |
1,121 posts held, back to 6 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 274 pages of Telegram’s post history, 20 posts per page.
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 230 of 236 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 1,121 (6 August 2026 – 18 November 2026) |
| Views total | 2,081,130 |
| Reactions total | 6,690 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 04:52 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.
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
13,983 reactions across 913 posts, in 50 distinct kinds. The most used accounts for 33.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4,704 | 33.6% | |
| 👍 | 3,305 | 23.6% | |
| 🖕 | 3,001 | 21.5% | |
| 🤣 | 646 | 4.62% | |
| 🤬 | 629 | 4.50% | |
| 👎 | 404 | 2.89% | |
| 😨 | 238 | 1.70% | |
| 🤔 | 123 | 0.88% | |
| 😱 | 111 | 0.794% | |
| 💩 | 106 | 0.758% | |
| 😭 | 81 | 0.579% | |
| 🤷♂ | 75 | 0.536% | |
| 🔥 | 72 | 0.515% | |
| 🥰 | 56 | 0.4% | |
| 😡 | 52 | 0.372% | |
| 👏 | 45 | 0.322% | |
| 🤮 | 45 | 0.322% | |
| 😢 | 34 | 0.243% | |
| 🤨 | 27 | 0.193% | |
| 🫡 | 23 | 0.164% | |
| 30 further kinds | 206 | 1.47% |
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 956 of the 1,000 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 13,983 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 13 August 2026 to 18 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’s own ‘edited’ marker: 1 of 236 posts held from the last 30 days (0.424%) 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).
📌 标题:品尝姐姐的母乳 👤 投稿者:云烟 洛 (🌟 萌新上路) 📦 资源详情:视频 4 个 📝 简介:我原本胸到B罩杯,感觉有点小,所以买了一点空运催乳剂打上,结果。这个药物的功效在我身上起到了翻倍的效果,从此以后,我就成了一头每天都要产出母乳的奶牛 🔗 进入精品频道 💬 评论区获取资源
👍3🤣1🥰1
Signed 成人大学投稿机器人2
📌 标题:太美了 好爽 👤 投稿者:匿名投稿者 📦 资源详情:图片 3 张,视频 3 个 📝 简介:无 🔗 进入精品频道 💬 评论区获取资源
🖕34🌭3🤬2😐1
Signed 成人大学投稿机器人2
📌 标题:把同学打印出來玩了 👤 投稿者:bro (☘️ 见习探员) 📦 资源详情:图片 1 张 📝 简介:无 🔗 进入精品频道 💬 评论区获取资源
🖕23🤷♂2❤1😨1
Signed 成人大学投稿机器人2
多个神秘邪恶的频道👇特殊的频道,小朋友禁止观看 🌰 全国精品处女研究所 | 🐕 恋母绿妈拉大车 🐕 嚣张集团每日直播频道 | 🤤 少妇人妻熟女控 🐕 女大学生性瘾集中地速约 | ❤️🔥 贫困少女扶贫中心 🫠 夜店酒吧醉酒捡尸 | 🫠 双飞女同姐妹 🍑 性瘾孕妇爱啪啪 | 🥰 破处开苞俱乐部 😉 恋母绿妈拉大车 | 🍑 少妇人妻熟女控 😋 巨乳肥臀微胖圈 | 🦵 精神小妹崩老头 🦶 嫩妹少女体检鉴穴中心 | 💖 女大学生约炮日记 🔞未成年人禁止加入🔞
❤3👍3
Signed 成人大学投稿机器人2
📌 标题:偷拍女友穿衣 第二期! 👤 投稿者:Xxky北 (🌟 萌新上路) 📦 资源详情:视频 2 个 📝 简介:第一期看到至少600多个兄弟看了女友奶子爽飞了 好奶就应该分享 老样子 求赞 然后继续发 🔗 进入精品频道 💬 评论区获取资源
👍64❤4
Signed 成人大学投稿机器人2
📌 标题:重庆骚货林佳铭被绿狗男友出卖,不露脸裸照被身边朋友看光,认出后找到绿狗对质,绿狗只能乖乖上交女友! 👤 投稿者:匿名投稿者 📦 资源详情:图片 22 张,视频 3 个 📝 简介:无 🔗 进入精品频道 💬 评论区获取资源
❤8🤣3🖕1🥴1
Signed 成人大学投稿机器人2
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_1922980900
Signed 极搜🔍资源搜索@JISOU
📌 标题:香港学生妹 👤 投稿者:匿名投稿者 📦 资源详情:视频 19 个 📝 简介:无 🔗 进入精品频道 💬 评论区获取资源
❤22🤬1
Signed 成人大学投稿机器人2
📌 标题:上贡骚货未婚妻 👤 投稿者:YM (🌟 萌新上路) 📦 资源详情:图片 6 张,视频 2 个 📝 简介:无 🔗 进入精品频道 💬 评论区获取资源
😨13👍4🖕2❤1
Signed 成人大学投稿机器人2
📌 标题:女友jk闺蜜 👤 投稿者:Suraj Pole (🌟 萌新上路) 📦 资源详情:图片 27 张,视频 6 个 📝 简介:投稿女友jk闺蜜 嘻嘻偷偷给她加料 问她酸不酸还细细品味 一脸骚样 赞多发后续 还有多位女主 🔗 进入精品频道 💬 评论区获取资源
👍80😨43🖕24❤6😡1
Signed 成人大学投稿机器人2
📌 标题:大一女友 👤 投稿者:Suraj Pole (🌟 萌新上路) 📦 资源详情:图片 47 张,视频 8 个 📝 简介:在教室做爱口交 三个月草了不低于200次 可惜是个贫乳 逼也被干黑了 标准反差眼镜母狗一个 赞多不停更 🔗 进入精品频道 💬 评论区获取资源
👍124🤣19❤10
Signed 成人大学投稿机器人2
📌 标题:免费的公交车 👤 投稿者:匿名投稿者 📦 资源详情:图片 2 张,视频 1 个 📝 简介:无 🔗 进入精品频道 💬 评论区获取资源
🖕19🤬6❤1😡1
Signed 成人大学投稿机器人2
Showing the 12 most recent of 1,121 posts we hold for @o_t_e_x. 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.
We recorded 74 posts on @o_t_e_x 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.
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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“成人大学(共创版)” (@o_t_e_x), 111,822 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/o_t_e_x.
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.