#双井 #凌芸 小少妇御姐98年身高165体重98🐻B+ 声音甜美 御姐服务 备注:龙哥 茶费:1K 🏳️:@lingyun7788999 双向:@linyun1122_bot 备注:龙哥 反馈:https://t.me/didulong/25420

Channel
北京 龙哥 北京修车 老师资料库
@aibeijing_01
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
36,265subscribers
+560 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001865376623 |
|---|---|
| Type | Channel |
| Username | @aibeijing_01 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/aibeijing_01 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 06:45 | 36,265 | +22 |
| 29 Aug 2026, 08:37 | 36,243 | +75 |
| 28 Aug 2026, 07:25 | 36,168 | +32 |
| 27 Aug 2026, 09:04 | 36,136 | +59 |
| 26 Aug 2026, 08:44 | 36,077 | +20 |
| 25 Aug 2026, 08:44 | 36,057 | +92 |
| 24 Aug 2026, 05:16 | 35,965 | +49 |
| 22 Aug 2026, 12:43 | 35,916 | -242 |
| 21 Aug 2026, 01:13 | 36,158 | -158 |
| 19 Aug 2026, 23:24 | 36,316 | +38 |
| 18 Aug 2026, 19:56 | 36,278 | +76 |
| 17 Aug 2026, 21:33 | 36,202 | +50 |
| 16 Aug 2026, 20:57 | 36,152 | +60 |
| 15 Aug 2026, 09:52 | 36,092 | +105 |
| 14 Aug 2026, 03:25 | 35,987 | +50 |
| 12 Aug 2026, 19:46 | 35,937 | +1 |
| 11 Aug 2026, 17:53 | 35,936 | +78 |
| 10 Aug 2026, 15:08 | 35,858 | +62 |
| 9 Aug 2026, 17:51 | 35,796 | +34 |
| 8 Aug 2026, 15:18 | 35,762 | first reading |
Engagement
96 posts held, back to 7 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 48 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.62%
- avg views ÷ 36,265 subscribers
- Avg views / post
- 950
- 96 posts measured
- Reaction rate
- 0.113%
- reactions ÷ views · ER floor
- Posts in window
- 96
- of 96 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 48 of 96 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 96 (7 August 2026 – 30 August 2026) |
| Views total | 91,204 |
| Reactions total | 67 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 05: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
- 9m 37s
- Average length
- 8s
Measured directly from 72 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.
Reaction mix
67 reactions across 37 posts, in 6 distinct kinds. The most used accounts for 92.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 62 | 92.5% | |
| 🎉 | 1 | 1.49% | |
| 👍 | 1 | 1.49% | |
| 👏 | 1 | 1.49% | |
| 🤪 | 1 | 1.49% | |
| 🫡 | 1 | 1.49% |
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 48 of the 96 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 67reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 96 most recent posts we hold, published 7 August 2026 to 30 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
#丰台 #大红门 #鑫鑫 南方妹子04年身高160体重90🐻B 备注:龙哥 茶费:8 ✈️:@zxinxin2004 双向:@zxx20040818_bot 备注:龙哥 反馈:https://t.me/didulong/25094 https://t.me/didulong/25112
#丰台 #石榴庄 #希月 个人贵州妹子年龄32身高160体重97🐻D 深喉口爆一绝 备注:龙哥 茶费:6 🏳️:@xiyuema 双向:@xiyeudndjsdfbot 💁:男群入口 💁:出击报备入会员 备注:龙哥 反馈参考: 📖 反馈报告 1 📖反馈报告2 📖 反馈报告3 📖反馈报告4 📖 反馈报告5 📖反馈报告6 📖 反馈报告 7 📖反馈报告8 📖反馈报告9 📖反馈报告10 📖反馈报告11
#百子湾 #念念 05年身高155体重40kg🐻B 准备:龙哥 茶费:1K 🏳️:@nianbba21 双向:@nianbba111222bot 备注:龙哥
#丰台 #石榴庄 #翠花妹妹 年龄27身高162体重100🐻B 水墨拉丝,双飞项目特色备注:龙哥 茶费:6 🏳️:@chuihuam 双向:@Chuandjdbot 💁:男群入口 💁:出击报备入会员 备注:龙哥 反馈参考: 📖 反馈报告 1 📖反馈报告2 📖 反馈报告3 📖反馈报告4 📖 反馈报告5 📖反馈报告6 📖 反馈报告 7 📖反馈报告8 📖 反馈报告 9 📖反馈报告10 📖 反馈报告11 📖反馈报告12 📖反馈报告13 📖反馈报告14 📖反馈报告15 📖反馈报告16
#百子湾 #冉冉 成都年龄21身高167体重96🐻B 俏皮可爱型 备注:龙哥 茶费:6 🏳️:@luckystar5072 双向:@luckystar5072bot 备注:龙哥 反馈参考: 📖 反馈报告 1 📖反馈报告2 📖 反馈报告3 📖反馈报告4 📖 反馈报告5 📖反馈报告6 📖反馈报告7 📖反馈报告8 📖反馈报告9
#天通苑 #小苹果 湖南 年龄27身高168体重50kg🐻B 备注:龙哥 茶费:9 🏳️:@xiaopingguo2024 双向:@xiaoxiao2024_bot 备注:龙哥
#朝阳 #百子湾 #果妮 年龄18身高165体重90🐻C 皮肤白 嫩妹 可上门 备注:龙哥 茶费:1K 🏳️:@guoni888 双向:@guoniBot 备注:龙哥
#草房 #娜娜 浙江年龄24身高168体重98🐻C 主动热情 温柔热情 备注:龙哥 茶费:6 🏳️:@beijingkaike 双向:@Nanade888bot 🏡:三个作业名额B套餐 8-2 600需要写反馈 备注:龙哥 反馈:https://t.me/didulong/21094 https://t.me/didulong/21409
#朝阳 #化工路 #大G 07年体重62kg🐻G 身高170 备注:龙哥 茶费:6 🏳️:@Ssssschunaiai 双向:@lovesichunbot 备注:龙哥 反馈:https://t.me/didulong/25304
#丰台 #成寿寺 #丹丹 身高173体重49kg🐻B 御姐 白瘦高 可女王调教 备注:龙哥 茶费:1K 🏳️:@Dd282702 双向:@Ddswj8888_bot 备注:龙哥 反馈参考: 📖 反馈报告 1 📖反馈报告2 📖 反馈报告3 📖反馈报告4 📖 反馈报告5 📖反馈报告6 📖 反馈报告 7 📖反馈报告8 📖 反馈报告 9 📖反馈报告10 📖 反馈报告11 📖反馈报告12
❤2
#亚运村 #小辣椒 年龄28身高160体重95 备注:龙哥 茶费:6 🏳️:@xiaolajiao12200 双向:@xiaolaj88_bot 备注:龙哥 反馈参考: 📖 反馈报告 1 📖反馈报告2 📖 反馈报告3 📖反馈报告4 📖 反馈报告5 📖反馈报告6
Showing the 12 most recent of 96 posts we hold for @aibeijing_01. 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 — 292,777 of 1,626,935entries 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 3 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“北京 龙哥 北京修车 老师资料库” (@aibeijing_01), 36,265 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/aibeijing_01.
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.