Channel
@hobglouqh
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
519subscribers
+0 since we began measuring on 1 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002211257805 |
|---|---|
| Type | Channel |
| Username | @hobglouqh |
| Description | 选妃流程：置顶有地区选择 先看频道已上架的看看有没有喜欢的，如果没有带着你的要求找到业务员进行定金找人 只要要求不太离谱3天内都能找到！ 公群护航:https://t.me/+JRptfeHec3cxNDZk 妹子交易走担保专群 切勿进行私下交易！ 下单请联系公群内业务员！ （所有bao养都是双发自愿无任何违法行，本频道妹子真实，已进行视频验证） 客服:@honglou2222 客服:@honglou3333 客服:@honglou5555 客服:@hlby8 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hobglouqh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 01:22 | 519 | no change |
| 1 Oct 2026, 00:47 | 519 | first reading |
5 posts held, back to 29 September 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 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 30 September 2026 |
|---|---|
| Posts held | 5 (29 September 2026 – 30 September 2026) |
| Views total | 5 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Oct 2026, 01:22 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 1 October 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.
Measured directly from 1 video 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.
编号：2609274351 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ ：星星015 省份： 青海 城市： 西宁 年龄：23 身高: 162 体重: 130 罩杯: 85b 职业：目前兼职 是否chu: 否 能否口：能 能否SM:能 能否无套（检测后）：能 能否内射：能 能否过夜：能 能否同居：暂定 有没有纹身：无 可否飞外省：能 可否出国：否 雷点（不接受）:下手太重 大姨妈日期：不稳定 每月陪伴天数：8 期望零花钱：6000(短期约会三天三千) 分几次支付零花钱：2 找金主的原因：恋爱加有钱花 最早出发时间：提前沟通 自我加分项：性格好，懂事，骚，瘾很大，会打游戏王者蛋仔瓦cs熊大快跑 介绍费6888 星星0614 联系客服：小熙 联系客服：小甜 联系客服：小萌 【便捷选妃-地区分类】
Signed 红楼上架机器人
编号：2609274341 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ y9877 省份: 青海 城市: 海东市 年龄: 21 身高:169 体重: 93 罩杯:C 职业: 无 是否是chu女: 否 月生活费多少: 3天9000 可不可以口: 🉑 SM能不能: 🉑 能不能无🍑（体检后）：🉑 分几次给生活费:2次 大概姨妈日期: 25号 能不能内🐍（体检后）：🉑 有没有纹身:无 是否可外省: 否 对老板雷点(不接受):无 可不可以同居: 🉑 是否可过夜: 🉑 （凌晨天亮前要回家） 短期可陪伴天数: 三天 找金主的原因: 缺零花钱 自我介绍加分项：温柔懂事 听话 骚 活儿好 💦多 人肉榨汁机🉑多p、颜射、口暴、🉑无🍑内🐍、肛门插入、户外暴露/玩弄、角色扮演、情趣玩具、项圈脚铐 等等SM 介绍费：7888 y A3…
Signed 红楼上架机器人
编号：2609272195 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ y5850 省份：青海L40 城市：西宁 年龄：22 身高：168 体重：150 🐻杯: c 职业：自由 能否飞外地：否 能否过夜/同居：可 是否抽烟/纹身:否 能否kou：可 能否体检后不d/🐍:否 预期费用：7k 每🈷️可陪天数:3天7k 能否接受sm :否 是否chu女: 否 可分几次付：2 姨妈时间：不固定 是否可去港澳；否 自我加分项： 雷点（不接受）: 介绍费：7888 y A5 联系客服：小熙 联系客服：小甜 联系客服：小萌 【便捷选妃-地区分类】
Signed 红楼上架机器人
编号：2609271875 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ ：xy1196 省份：青海 城市：民和 年龄：18 身高：173 体重：106 职业：学生 罩杯：C 星座：双子座 雷点（不能接受）：不喜欢太色的，不喜欢太胖的，个子小的，长得丑的 是否chu女:不 能否接受SM：不能接受 能否接受无套： 不能接受 能否接受口：不能 可同居：在上学只能陪白天 可过夜：在上学只能陪白天 可陪伴天数:3 可否其他城市：不能 可否飞往外省：不能 姨妈期：26号 接受到手多少：1800 妹子费用支付方式：微信转账2次（几次付款） 自我加分项：满分 身材好， 要求：脾气要好，要爱我，有了我不能找其他的女生，我喜欢小惊喜，我不开心你得哄我，不能骗我，答应我的每一件事都要做到，有车，要有高工资的工作，不可以太色 介绍费：6888 小雅 Z 联系客服：小熙 联系客服：小甜 联系客服：小萌 【便捷选妃-地区分类】
Signed 红楼上架机器人
编号：2609270742 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ ：李逍遥九2093 李︂逍︅遥9.2 省份: 青海 城市: 西宁 目前︁状︆态︆: 雪︎生͏ 最︀高︃学︅历︇: 大︃专︈ 年龄︈: 19 身︌高︊: 168 体重︄: 110͏͏͏ 罩︂杯大︌小︍: c 是︌不️是chu: 否͏ 检︍查︂后︃能︈否︍不戴︍t: 能（内︌+520/次）͏ 能否用︈嘴︄: 目︈前︎不︌会︈（但可以︌学︌）͏ 能不能接受︀SM: 仅︁限︋轻度͏͏ 能︇否︄长︂期︍同︉居︊: 否︍͏ 能︌否留宿︆过︅夜︆: 能︍ 能︈否︃跨︌省︉动身︃: 能 大︂姨︌妈日︉期︍: 20 有︄没︉有︋纹身️: 无︍͏ 最︈早何︂时︃出发: 周末︀ 每月︅陪同︊天︄数：3͏ 每︌月︊生︌活︇费︆: 5000͏…
Signed 红楼上架机器人
Showing the 5 most recent of 5 posts we hold for @hobglouqh. 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.
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.
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“青海包养伴游【红楼选妃馆】” (@hobglouqh), 519 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/hobglouqh.
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.