北京商务KTV 全新娱乐体验|每晚人气满座|青春主场|玩法升级 ⏰⌚️📱📲💻🧾 🥳聚集百位高颜值00后活力伙伴沉浸式互动体验,现场氛围超燃大胆玩法。亲密接触。情绪直达巅峰热辣氛围。贴身互动。气氛热烈持续 🤘专属亮点:融合沉浸环境,趣味游戏与主动互动,超越派对定义,升级你的感官体验! ❤️承诺服务:专注极致氛围|营造私密感|焕发青春能量|全场自由开放,随性玩乐 ❗️❗️❗️靠谱又放心 本人驻场亲自安排 📱 13903278322 📱 @Mikuu3292 双向机器人 @cbeijingKTV_bot #北京商k #北京KTV #北京荤场 #北京真空游戏场 #北京摸摸唱

Channel
北京出击资源(认证)
@pocketminiapp
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
26,517subscribers
-440 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001611700194 |
|---|---|
| Type | Channel |
| Username | @pocketminiapp |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/pocketminiapp |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 10:24 | 26,517 | -490 |
| 26 Aug 2026, 11:52 | 27,007 | +11 |
| 25 Aug 2026, 09:47 | 26,996 | -4 |
| 24 Aug 2026, 13:02 | 27,000 | +41 |
| 22 Aug 2026, 17:34 | 26,959 | -11 |
| 21 Aug 2026, 10:44 | 26,970 | +13 |
| 20 Aug 2026, 22:46 | 26,957 | first reading |
Engagement
9 posts held, back to 24 May 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 14 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 15.7%
- avg views ÷ 26,517 subscribers
- Avg views / post
- 4,150
- 6 posts measured
- Reaction rate
- 0.019%
- reactions ÷ views · ER floor
- Posts in window
- 6
- of 9 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 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 August 2026 |
|---|---|
| Posts held | 9 (24 May 2026 – 25 August 2026) |
| Views total | 24,921 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Aug 2026, 08:50 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
- 41s
- Average length
- 14s
Measured directly from 3 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
6 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 66.7% | |
| 🤔 | 1 | 16.7% | |
| 🤗 | 1 | 16.7% |
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 5 of the 9 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 24 May 2026 to 25 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
以前双向机器人坏了,有事请联系这个☎️ @xianfongxiaobot
【艺名】: #倩儿 【地址】: #朝阳区 【联系】: @chenchen1789 【频道】: https://t.me/bjinchenchen 👇下面评论区留言👇
🤗1
北京商k北京KTV北京情趣游戏场 签到80+,亲摸不躲,热情似火 帝王级享受 📱📱📱📱 📱 📱 📱 📱 📱 情绪价值拉满,从倒酒剥瓜子到贴身热舞 沙发秀,高山流水,冰火,九宫格,舌尖缠编全程零冷场,玩到你腿软关键不乱加价,做的口碑服务一流 价格透明 酒水不贵 主要经济实惠玩的开心 北京最好玩的KTV,情趣游戏场,游戏精彩刺激 ------------------------------- 联系客服:@BST899 微信客服:jj16561 双向机器人: @BST899_bot 客服电话:13127723272 频道展示:https://t.me/BST88999 (支持U支付) #北京商K #北京KTV #北京商务KTV #北京游戏场
❤1
【艺名】: #水妹 【地址】: #朝阳区 【联系】: @sm6635 【频道】: https://t.me/sm663 👇下面评论区留言👇
❤1
✅全国低中高端外围✅ https://t.me/vuvvvvvvvvv
✅全国低中高端外围✅ https://t.me/vuvvvvvvvvv
❤2
✅全国低中高端外围✅ https://t.me/vuvvvvvvvvv
【艺名】: #馨儿 【地址】: #平谷区 【联系】:@xinger22 【频道】:https://t.me/xinxin08890 👇下面评论区留言👇
🤔1
Showing the 9 most recent of 9 posts we hold for @pocketminiapp. 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.
Posts edited after publishing
@pocketminiapp edited 1 post 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.
- First edit seen
- 22 August 2026
- Most recent edit
- 22 August 2026
Citation-graph rank
Citation-graph rank — 1,123,256 of 1,621,120entries 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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“北京出击资源(认证)” (@pocketminiapp), 26,517 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/pocketminiapp.
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.