私密频道 : https://t.me/+r_YsCwQLGkgzZDI1
❤2

Channel
@DJRxuanmei
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
7,222subscribers
-1,818 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003762138280 |
|---|---|
| Type | Channel |
| Username | @DJRxuanmei |
| Description | 群: https://t.me/+6yfO0Iq5TjAxZGNk 看妹频道: @DJRBY1 各位老板订阅一下(每日更新) 备用频道: @DJRBY2 @DJRBY3 @DJRBY4 @DJRBY5 @DJRBY6 @DJRBY7 @DJRBY8 @DJRBY9 客服: @DJRkefu 双向机器人: @DJRKFBOT 智能机器人: @DJRZDSCBOT |
| Created | Between 1 February 2026 and 3 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/DJRxuanmei |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 |
|---|---|---|
| 9 Nov 2026, 01:51 | 7,222 | +83 |
| 5 Nov 2026, 22:09 | 7,139 | -12 |
| 2 Nov 2026, 13:30 | 7,151 | -9 |
| 30 Oct 2026, 18:27 | 7,160 | -37 |
| 27 Oct 2026, 15:56 | 7,197 | -21 |
| 24 Oct 2026, 05:46 | 7,218 | -2 |
| 21 Oct 2026, 07:58 | 7,220 | -18 |
| 18 Oct 2026, 16:15 | 7,238 | -12 |
| 15 Oct 2026, 10:00 | 7,250 | -52 |
| 12 Oct 2026, 11:01 | 7,302 | -40 |
| 5 Oct 2026, 14:59 | 7,342 | +41 |
| 27 Sept 2026, 13:35 | 7,301 | -9 |
| 18 Sept 2026, 04:58 | 7,310 | -204 |
| 14 Sept 2026, 00:56 | 7,514 | -257 |
| 10 Sept 2026, 11:37 | 7,771 | -463 |
| 4 Sept 2026, 20:59 | 8,234 | -320 |
| 1 Sept 2026, 04:05 | 8,554 | -173 |
| 29 Aug 2026, 10:44 | 8,727 | -149 |
| 26 Aug 2026, 15:58 | 8,876 | -50 |
| 23 Aug 2026, 12:06 | 8,926 | first reading |
19 posts held, back to 3 March 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 32 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.
| Window | Rolling 30 days · latest post in window 14 October 2026 |
|---|---|
| Posts held | 19 (3 March 2026 – 14 October 2026) |
| Views total | 5,810 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 08:40 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 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
253 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 232 | 91.7% | |
| 👍 | 10 | 3.95% | |
| 😁 | 7 | 2.77% | |
| 👎 | 2 | 0.791% | |
| 🏆 | 1 | 0.395% | |
| 👏 | 1 | 0.395% |
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 16 of the 19 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 253 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 3 March 2026 to 14 October 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: 0 of 1 post held from the last 30 days (0%) 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).
私密频道 : https://t.me/+r_YsCwQLGkgzZDI1
❤2
东京热包养指南 pinned «👉一. 安排流程 : 频道挑选需要bao养的妹子,联系客服进选妃频道确认bao养对象,确认好后支付介绍费,然后安排双方线下见面,bao养费是给妹子本人,平台不收取任何bao养费【未见到妹子全额退介绍费】介绍费支持担保交易。150u进会员群 👉提前付介绍费用,再安排妹子线下见面【未见到妹子全额退介绍费用】介绍费可担保交易 👉都是真实妹子 所有详细资料都是谈出来的。不用怀疑真实度 都有本人真实微信视频认证过。 如果见到女孩满意,此单完成(需提前支付女孩路费及介绍费)。 金主方需在与女孩见面 半小时内 回复满意或不满意(不回复默认满意…»
私密频道 : https://t.me/+r_YsCwQLGkgzZDI1 看妹网站: https://jkpru.com/#/login https://xinshangren.vip/?entry=backup-card-20260917
❤8👍1
@BYQBLbot 免费版 @BYQBLbot 免费版 @BYQBLbot 免费版 📖 使用说明 🚨 提交曝光 上传真实照片,填写诈骗经过,提交后等待管理员审核。 🔍 人脸查询 发送 1 张照片,系统自动检索曝光库,命中则返回曝光详情。 🔎 关键词查询 请输入要搜索的关键词(2–64 字符),例如: • 身份证号码 • 微信号 / QQ 号 • 手机号码 • 姓名或其他标识信息 🔥🔥🔥欢迎各位平台,聊手,老板来投稿🖥 🚨全网真实曝光⚠️捞女 ⚠️跑路女 ⚠️鸽子女 ⚠️骗子 小编承诺🎉: 不偏袒任何垃圾平台,不推荐任何正规平台 只做曝光,避雷。照亮狼友们的性福时光
❤28👏1
选妃网站: https://xinshangren.vip
❤11
高手进阶指南: 1、有钱从来不缺好女孩,没必要花钱还得低声下气看对方脸色,小头绝对不能控制大头,你才是上帝。 2、要学会拒绝,二哈成不了狼,舔狗上不了床,越是让步对方就越是得寸进尺蹬鼻子上脸。 3、不要过分上头,别被妹子牵着鼻子走,钱是给妹子看的,不是给妹子花的, 4、别让感性战胜理性,卖惨有时候比卖肉赚的多的多,乐一乐就好,不要心陷其中,最终人财两空。 5、不要透露自己太多的私密,真诚不是必杀技,真诚是杀死你自己的必杀技。 6、锁好自己的房门,保护好自己的财物。 最后、万花丛中过,片叶不沾身,深情只是入场券,套路才是天花板
❤34
VIP私推专用: https://t.me/+r_YsCwQLGkgzZDI1 客服: @DJRBY 看妹机器人: @DJRZDSCBOT 选择订阅小妹,机器人会按您的需求自动推送 双向 地区选择 交流大群 安排流程 导航 客户反馈 曝光查询 外围频道 网站: xinshangren.vip 为方便广大新老会员,解决会员需求,特此推出全国大圈外围,解决会员更多需求 选妃频道: https://t.me/+99-gf9xVxYZiZGFi 选妃联系: @tongdaoWW 无法私聊: @TDWWBOT 1.外围妹妹各种类型都有! 2.妹妹都是兼职流动性大! 3.外围是实时选人!为确保时间上不冲突需要意向金过滤口嗨!介意勿扰!
❤31👍3
《东京热》全球苞养高端定制平台,行业顶尖专业专注靠谱推荐 。 各大在校雪生、往届bi业生、职场小姐姐、老shi,hu士,模特,空jie,母nv,双包胎,苞养定制服务,全网独家一手资源,学信网可查,真实身份可查,非小jie外wei冒充,欢迎同行拉手合作,茶水费丰厚,可带徒弟。(没有的地方可以100u定金找同城)全球都可以安排。 看妹频道: @DJRBY1 各位老板订阅一下(每日更新) 备用频道: @DJRBY2 @DJRBY3 @DJRBY4 @DJRBY5 @DJRBY6 @DJRBY7 @DJRBY8 @DJRBY9 资源大群:https://t.me/+6yfO0Iq5TjAxZGNk 永久导航: @DJRZG 智能机器人: @DJRZDSCBOT
❤17👎2🏆1
🔥 全网最真实包养客户反馈,陆续更新实战视频+实战报告+反馈! 全部在实战群!全网有偿采集最真实的出击报告,带爱爱视频最佳! 文字描述66u,文字+视频188u,每月最高点赞量的奖励666u,全年最高点赞量的奖励1666u。 需提供真实出击截图+妹子资料,不限平台只求真实! 所有报告下面链接都是对应相应得妹子! 宗旨日回本! 灌满蛋白质! 全部真实靠谱,永保售后! 最近很多平台做假报告,假成交,诱导消费!!! 我们只做最真实的报告,全网可查可核对! (如果有一份假得报告,此妹子全部免单!) (全网出现的女孩包养圈都是一手更新,别人有的我们肯定有,我们有的别人不一定有! ) 实战视频+实战报告+反馈! 全部在实战群! 禁止转发! 禁止截图! 实战会员专享福利! (刷锅透露给妹子 直接永久踢出) 只做真实素人! 值得你拥有!体验 完美性福生活! 部分请看评论区
❤34👍1
https://t.me/DJRZG?boost
❤4
《东京热》:专注包养行业5年!全球包养学生妹|处女|萝莉 🔰核心价值:服务好每一位客户,为客户的性福生活完美承接。 🔰东京热传媒是一家以服务为平台价值的包养平台,从事包养行业期间一直是行业标杆!明星平台!一直被模仿从未被超越! 东京热包养永久用户名: @DJRZG (东京热中国) 客服:@DJRBY 私推专用 https://t.me/+r_YsCwQLGkgzZDI1 中圈: https://t.me/TDWWZQ
❤18👍4😁3
《东京热》全球苞养高端定制平台,行业顶尖专业专注靠谱推荐 。 各大在校雪生、往届bi业生、职场小姐姐、老shi,hu士,模特,空jie,母nv,双包胎,苞养定制服务,全网独家一手资源,学信网可查,真实身份可查,非小jie外wei冒充,欢迎同行拉手合作,茶水费丰厚,可带徒弟。(没有的地方可以100u定金找同城)全球都可以安排。 看妹频道: @DJRBY1 各位老板订阅一下(每日更新) 备用频道: @DJRBY2 @DJRBY3 @DJRBY4 @DJRBY5 @DJRBY6 @DJRBY7 @DJRBY8 @DJRBY9 资源大群:https://t.me/+6yfO0Iq5TjAxZGNk 永久导航: @DJRZG 智能机器人: @DJRZDSCBOT
❤22😁4👍1
Showing the 12 most recent of 19 posts we hold for @DJRxuanmei. 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.
@DJRxuanmei edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 9 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“东京热包养指南” (@DJRxuanmei), 7,222 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/DJRxuanmei.
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.