编号:2608091081 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 昵称:小野438 Q0097 所在省份:内蒙古 所在城市:乌兰浩特 称呼:小琦 雪生还是工作:雪生 学历:高中 年龄:18-1 身高:163 体重:138 罩杯:C 是否chu:否 体检后能否无t:不可以 是否可以内S:不可以 能否口: 可以 SM能不能:能 能否同居:能 能否过夜:能 能否去其他省份:近的可以 例假日期:每月开头 有没有纹身:没有 最早出发时间:假期 短期3天零花钱:2K 短期7天零花钱:4.5K 零花钱分(2)次结清 自我评价(加分项):长得还可以 不能接受金主(雷点):不要太矮 介绍费:7888 小野 100U入会,首单6折,单单打折 #内蒙包养 #呼和浩特包养 #包头包养 💰支持比价介绍费可给最低 包养须知➡️➡️ @txxr888 ⚠️骗子曝光 @baomei888 🤖双向机器人 @tianxinba…

Channel
内蒙包养|甜心包养内蒙频道
@txnm8888
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
62subscribers
-21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003453056461 |
|---|---|
| Type | Channel |
| Username | @txnm8888 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/txnm8888 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 19:02 | 62 | -4 |
| 21 Aug 2026, 09:27 | 66 | -5 |
| 15 Aug 2026, 10:35 | 71 | -12 |
| 9 Aug 2026, 17:47 | 83 | no change |
| 7 Aug 2026, 20:02 | 83 | first reading |
Engagement
5 posts held, back to 9 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
- 1.61%
- avg views ÷ 62 subscribers
- Avg views / post
- 1.0
- 5 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- 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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 5 (9 August 2026 – 9 August 2026) |
| Views total | 5 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 17:47 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
- Video runtime
- 1m 11s
- Average length
- 24s
Measured directly from 3 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.
Recent posts
编号:2608090979 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 昵称:mc3989 省份: 内蒙古 城市: 鄂尔多斯 年龄: 27 身高: 172 体重: 106 罩杯:b 职业: 事业单位行政 是否是chu女: 否 月生活费多少:三天8K 可不可以口: 可 SM能不能: 轻微m 能不能无🍑(体检后):不能 分几次给生活费: 两次 大概姨妈日期: 7号 能不能内🐍(体检后):否 有没有纹身: 有 是否可外省: 是 对老板雷点(不接受):体臭, 可不可以同居: 否 是否可过夜: 可以 月可陪伴天数: 连续3天 找金主的原因:不想和普通男生接触 自我介绍加分项:听话.会喝酒,不纠缠 颜射 囗暴射嘴里 控制高潮 滴蜡 窒息 项圈脚铐 模似强奸 情趣玩具 介绍费7888空白N9 888RMB入会,单单享折扣 #内蒙包养 #呼和浩特包养 #包头包养 ❤️甜心包养 专注内蒙包养 包养须知➡️➡️ @t…
编号:2608090869 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ af201 昵称:WZS102 省份:内蒙古 城市:包头 年龄:28 身高:170 体重:120 罩杯:B+ 学历:大学 职业:主播 是否是chu女:否 可不可以kou:可 能不能内s:否 能不能无t:否 SM能不能:能 有没有纹身:无 是否可外省:可以 是否可过夜:可以 可不可以同居:否 月可陪伴天数;3 月生活费:1w 自我介绍加分项:听话不粘人 对另一半的要求:温柔性格稳定 对老板雷点(不接受): 无 介绍费6888TT 888RMB入会,单单享折扣 #内蒙包养 #呼和浩特包养 #包头包养 ❤️甜心包养 专注内蒙包养 包养须知➡️➡️ @txxr888 ❤️甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot 🏆入会联系客服看视频认证
编号:2608090791 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 省份:内蒙古 地区:阿拉善左旗 年龄:18-1 身高:168 体重:102 罩杯:B 学历:糕中 职业:雪生 是否chu:否 有无纹身:无 生理期:月中 是否能去外省:否 能否过夜:否 能否同居:否 月陪伴天数:3 生活费期望:4k 能否无套:否 能否内射:否 能不能口:可 sm接受程度:否 自身优点: 温柔微粘人,能提供情绪价值,反差!!! 金主雷点:肥胖 年龄大 加菲猫k101 介绍费:7888 888RMB入会,单单享折扣 #内蒙包养 #呼和浩特包养 #包头包养 ❤️甜心包养 专注内蒙包养 包养须知➡️➡️ @txxr888 ❤️甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot 🏆入会联系客服看视频认证
编号:2608090736 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 省份:内蒙古 地区:呼伦贝尔 年龄:19 身高:168 体重:54 罩杯:B 雪生/工作:学生(非全日制) 纹身抽烟:无 是否chu女:是chu 金主体检后无套(不内🐍):不接受不带套,做的话必须戴套!(保证安全可以商量) 能不能内:不能 能否接受口:不接受 可同居:可 可过夜:可 可陪伴天数:1.5 30天 可否飞往外省:可 多久可以出发:确定一周内就可 接受到手多少: 姨妈期:4~5天 妹子费用支付次数:(几次付款)2 介绍费:11888 GG 888RMB入会,单单享折扣 #内蒙包养 #呼和浩特包养 #包头包养 ❤️甜心包养 专注内蒙包养 包养须知➡️➡️ @txxr888 ❤️甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot 🏆入会联系客服看视频认证
Showing the 5 most recent of 5 posts we hold for @txnm8888. 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.
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.
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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“内蒙包养|甜心包养内蒙频道” (@txnm8888), 62 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/txnm8888.
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.