⚠️ 请勿给妹妹现场展示本频道 🌟🌟 查看北京顶美频道 🌟🌟 查看北京大圈频道 🌟🌟 查看北京中圈频道 🌟🌟 高端外围导航入口 🌟🌟 包养包月导航入口 🌟🌟 客户评价反馈频道 🌟🌟 客服大蜜:@lo080 🌟🌟 双向客服:@lo080bot

Channel
北京外围/北京包养/北京上门/北京学生会
@BJbeijing
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7,893subscribers
-31 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001339583583 |
|---|---|
| Type | Channel |
| Username | @BJbeijing |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/BJbeijing |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 16:45 | 7,893 | -3 |
| 19 Aug 2026, 08:57 | 7,896 | -18 |
| 16 Aug 2026, 01:48 | 7,914 | -8 |
| 12 Aug 2026, 09:12 | 7,922 | -2 |
| 12 Aug 2026, 01:46 | 7,924 | first reading |
Engagement
23 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 11 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.32%
- avg views ÷ 7,893 subscribers
- Avg views / post
- 420
- 23 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 23
- of 23 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 23 August 2026 |
|---|---|
| Posts held | 23 (9 August 2026 – 23 August 2026) |
| Views total | 9,666 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Aug 2026, 05:04 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
- Photos
- 388
- Videos
- 174
- Links
- 109
Lifetime counters from Telegram’s own channel header, read 25 August 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.
- Video runtime
- 2m 33s
- Average length
- 9s
Measured directly from 18 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
艺名 小图图 年纪09年 身高159 体重 42KG 罩杯C 籍贯 江苏 特点:三点粉嫩 鲍鱼薛 超灵敏感,一碰就出水 叫声动听 让课流连忘返 性格主动热情
姓名:琉璃 身高:165 年龄:00年 胸围:36D 服务介绍 胸大活好,极品身材,热情主动,爱意溝满,互动调情,鸳鸯浴,老汉推车,观音坐莲,过水,胸推,指划,口吹
芳名:欧阳 1年龄:22 身高:166 体重:45幕胸围:36c 外出:可外包夜:不包夜 优点:鲜嫩多汁温柔,乖巧听话,丝袜诱惑,制服诱惑,配合各种姿势,私密紧致,
芳名:爱莉 色产地:河北 胸围:B+ 净年龄:21 身高:167 &体重:86斤 :上课内容:蛇吻 胸推 指划 足交 丝袜高根 情趣玩具,口活好+口爆 69式爆吸
艺名:诗瑶 祖籍:河北 年龄:07, 身高168,体重:49kg 学生兼职,刚下海,温柔随和,热情主动, 内容:陪洗澡,裸吹,高跟鞋情趣制服,丝袜
刚到新人:雅茹 年龄.21 净身高:170 胸围:36D 体重:45kg 皮肤白净 敏感体质 易高潮 舌吻心
艺名露蕗 初下海,身高172 体重 49kg 芳龄25 胸围36c 高挑极品御姐, 服务,丝袜诱惑,舌吻 吹箫 调情 性格温和配合度高 真人对版 互动配合, 90分钟两水,自带工作室
艺名:问问 产地:河南 胸围:b 身高:170 体重:105 可外出可69 特点:嫩 润 滑
极品兼职学妹 Name:南汐 Age:05年 Heiget: 175cm Bust:&D Service:可亲可口可690可陪浴 态度好 主动热情 可爱听话配合 不催不事 情趣 丝袜随身带
年龄:04年 身高:165 🐻B 特色:清纯秀丽 课程:吸蛋蛋 情趣内衣 丝袜诱惑 没工作室,只外出
• Rec 艺名:星星 年龄:08年 身高:168 体重:45kg 清纯学生短暂停留 中圈90分钟/两💦
Showing the 12 most recent of 23 posts we hold for @BJbeijing. 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.
Citation-graph rank
Citation-graph rank — 1,172,828 of 1,602,822entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“北京外围/北京包养/北京上门/北京学生会” (@BJbeijing), 7,893 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/BJbeijing.
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.