Telegram RegisterThe public register of Telegram
Telegram profile photo for 【北京·作业报告反馈】

Channel

【北京·作业报告反馈】

@BJ8186

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

7,470subscribers

+143 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002603420082
TypeChannel
Username@BJ8186
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/BJ8186

Growth

7,3267,4707,3987 August 2026 — 7,327 subscribers7 August 2026 — 7,327 subscribers7 August 2026 — 7,326 subscribers10 August 2026 — 7,342 subscribers14 August 2026 — 7,354 subscribers17 August 2026 — 7,392 subscribers20 August 2026 — 7,393 subscribers24 August 2026 — 7,430 subscribers26 August 2026 — 7,427 subscribers30 August 2026 — 7,450 subscribers2 September 2026 — 7,470 subscribers7 August 20262 September 2026
11 measurements spanning 26 days, net +143. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 7,304–7,492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 12:337,470+20
30 Aug 2026, 05:237,450+23
26 Aug 2026, 22:277,427-3
24 Aug 2026, 03:127,430+37
20 Aug 2026, 13:167,393+1
17 Aug 2026, 09:567,392+38
14 Aug 2026, 03:267,354+12
10 Aug 2026, 21:427,342+16
7 Aug 2026, 23:187,326-1
7 Aug 2026, 19:477,327no change
7 Aug 2026, 19:387,327first reading

Engagement

65 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 13 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.20%
avg views ÷ 7,470 subscribers
Avg views / post
89.9
63 posts measured
Reaction rate
1.10%
reactions ÷ views · ER floor
Posts in window
63
of 65 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. It is computed over the 3 of 63 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held65 (6 August 202628 August 2026)
Views total5,661
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 23:06 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.

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.0%

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 3 of the 65 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 65 most recent posts we hold, published 6 August 2026 to 28 August 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.

Recent posts

28 Aug 2026, 16:46 UTC16 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#菲菲 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #大兴 #南五环 #亦庄 🔗 :https://t.me/BJ5187/133960?single 📋 :北京联盟 @BJ8689 ✍ :菲菲老师回复速度很快,人非常热情,教室环境很宽敞,收拾的很干净,人比照片好看,口活很棒,很耐心,没说停就一直口,下面很紧,过程非常投入,超级棒的一次体验

28 Aug 2026, 11:59 UTC45 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#美丹丹 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #丰台 #南四环 #公益西桥 🔗 :https://t.me/BJ5187/136136?single 📋 :北京联盟 @BJ8689 ✍ :去了美丹丹和小美彤双飞,两个老师的情绪价值很高,从进门开始就挑逗个不停,床上,俩人左右开攻从胸一路舔到弟弟,两人共吃一棒,各种姿势和玩法都ok~啪啪还可以不换套,很爽

28 Aug 2026, 11:59 UTC44 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#小美彤 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #丰台 #南四环 #公益西桥 🔗 :https://t.me/BJ5187/135730?single 📋 :北京联盟 @BJ8689 ✍ :去了美丹丹和小美彤双飞,两个老师的情绪价值很高,从进门开始就挑逗个不停,床上,俩人左右开攻从胸一路舔到弟弟,两人共吃一棒,各种姿势和玩法都ok~啪啪还可以不换套,很爽

28 Aug 2026, 09:30 UTC197 viewsread 28 August 2026
Photo

👩🏻‍🏫 #清漪 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #东三环 #双井 🔗 :https://t.me/BJ5187/134096?single 📋 :北京联盟 @BJ8689 ✍ :二刷清漪老师 柔式和泰式俱佳 浅聊之下 才发现年纪虽轻 技法出众 情商极高 推荐之

28 Aug 2026, 03:55 UTC57 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#安妮 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #北四环 #亚运村 🔗 :https://t.me/BJ5187/138201?single 📋 :北京联盟 @BJ8689 ✍ :关注亚运村安妮妹妹很久,终于有机会深入交流,提前定好时间 商场车库见面,妹妹情商很高,聊天自然舒服不会冷场尴尬,很爱干净,给我擦的很仔细也很温柔,口活很顶 配合度高,骚话不断,顶级少妇感,身材也很哇塞!已经开始期待下一次的见面了!

27 Aug 2026, 13:00 UTC78 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#安妮 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #北四环 #亚运村 🔗 :https://t.me/BJ5187/138201?single 📋 :北京联盟 @BJ8689 ✍ :出击了亚运村野战王 安妮: 体验感拉满,开始很紧张很激动,老师下面特别紧,爱爱的时候说话特别sao,配合度拉满,很适合寻求刺激,女上的时候九浅一深容易被秒掉,期待下次!

27 Aug 2026, 04:31 UTC634 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#芊芊 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #北四环 #亚运村 🔗 :https://t.me/BJ5187/140390?single 📋 :北京联盟 @BJ8689 ✍:约好老师,直接开车过去,声音很好听,打扮也是我喜欢那种 ,聊了一会就一起洗澡,洗完老师叫我躺下,慢慢的给我口起来,口技真的还可以,还舔了蛋蛋,差点没忍住,马上就开始配合我,简直酥麻了,马上把老师翻过来,老师一边享受一边用手拿上早准备好的tt,很快速的帮我带上帽子,我们床上换了几个姿势,其中有一大半都是老师主动引导的,不得不说,老师看着可爱活泼那种,骨子里也是骚骚的,还会不停的叫老公,在耳边吹气,爽歪歪,直到结束洗完澡回家路上都在回味,期待下次了。

26 Aug 2026, 08:18 UTC124 views1 reactionsread 28 August 2026
Photo

👩🏻‍🏫 :#安妮 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #北四环 #亚运村 🔗 :https://t.me/BJ5187/138201?single 📋 :北京联盟 @BJ8689 ✍ :今天本来想和安妮老师玩一个中项,体验一下在车上的感觉,没想到老师知道了我还是第一次,就问我要不要艹她(骚姐姐太好了)。口完直接帮我戴好套,我还没反应过来,就被塞进了老师湿润紧致温暖的b里。最后也是和老师一起同时高潮太爽啦。

1

26 Aug 2026, 06:11 UTC112 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#小白菜 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #东四环 #化工 🔗 :https://t.me/BJ5187/139738?single 📋 :北京联盟 @BJ8689 ✍ :小白菜 进出方便,房间干净 服务用心,真实水多 日感美妙,紧致水多

26 Aug 2026, 06:09 UTC104 viewsread 28 August 2026
Photo

👩🏻‍🏫 :#雪琪 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #丰台 #西二环 #六里桥东 🔗 :https://t.me/BJ5187/140498?single 📋 :北京联盟 @BJ8689 ✍ :飞哥交个六里桥雪琪的作业。这次cj雪琪总体来说不大尽兴。妹子虽说身材还可以,但没什么服务,也没什么话。一直都是我在找话头。妹子抽烟挺凶,嘴里一股烟油子味。再一个,妹子没有固定的教室,用的时租房。我是不喜欢的。总之性价比不高

20 Aug 2026, 08:43 UTC18 viewsread 20 August 2026
Photo

👩🏻‍🏫 :#娇娇 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #东五环 #草房 🔗 :https://t.me/BJ5187/136738?single 📋 :北京联盟 @BJ8689 ✍ :出击娇娇,约的pp 去的时候她姐妹也🈳,于是改了双飞,洗完到床上做服务,ls口活也很好,差点给我口出来,立即叫停,戴上雨伞,让表妹抱着娇娇ls对着我 直接开造,可以换着插,但是得换套有点麻烦,不过也很理解,大战几个回合出货,休息了10几分钟,第二发开始,毒龙 深喉 超级爽,第二次时间有点久做不出来,还是表妹 手口并用 顺利出货,好评晚上推荐哥们儿去。

20 Aug 2026, 08:42 UTC19 viewsread 20 August 2026
Photo

👩🏻‍🏫 :#表妹 👍 : (5⭐满分) ⭐⭐⭐⭐⭐ 🌎 : #朝阳 #东五环 #草房 🔗 :https://t.me/BJ5187/136756?single 📋 :北京联盟 @BJ8689 ✍ :出击娇娇,约的pp 去的时候她姐妹也🈳,于是改了双飞,洗完到床上做服务,ls口活也很好,差点给我口出来,立即叫停,戴上雨伞,让表妹抱着娇娇ls对着我 直接开造,可以换着插,但是得换套有点麻烦,不过也很理解,大战几个回合出货,休息了10几分钟,第二发开始,毒龙 深喉 超级爽,第二次时间有点久做不出来,还是表妹 手口并用 顺利出货,好评晚上推荐哥们儿去。

Showing the 12 most recent of 65 posts we hold for @BJ8186. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 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.

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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“【北京·作业报告反馈】” (@BJ8186), 7,470 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/BJ8186.

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.