Channel
@bjthb2
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
31,755subscribers
+328 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001417244931 |
|---|---|
| Type | Channel |
| Username | @bjthb2 |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/bjthb2 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 01:47 | 31,755 | +12 |
| 28 Aug 2026, 00:54 | 31,743 | +99 |
| 26 Aug 2026, 22:36 | 31,644 | +36 |
| 25 Aug 2026, 22:37 | 31,608 | +11 |
| 25 Aug 2026, 00:48 | 31,597 | +49 |
| 23 Aug 2026, 12:37 | 31,548 | +19 |
| 21 Aug 2026, 20:29 | 31,529 | +20 |
| 20 Aug 2026, 15:58 | 31,509 | +40 |
| 19 Aug 2026, 14:04 | 31,469 | +19 |
| 18 Aug 2026, 17:14 | 31,450 | +30 |
| 17 Aug 2026, 15:17 | 31,420 | +13 |
| 16 Aug 2026, 08:54 | 31,407 | -60 |
| 14 Aug 2026, 19:46 | 31,467 | +21 |
| 13 Aug 2026, 08:16 | 31,446 | +27 |
| 12 Aug 2026, 11:24 | 31,419 | -8 |
| 11 Aug 2026, 17:45 | 31,427 | no change |
| 11 Aug 2026, 17:31 | 31,427 | first reading |
5 posts held, back to 5 June 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 33 pagesof 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 23 August 2026 |
|---|---|
| Posts held | 5 (5 June 2026 – 23 August 2026) |
| Views total | 2,958 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 18:32 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.
Measured directly from 5 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.
🍓北京摸摸唱KTV-死摸死亲❗️ 如果你觉得摸摸唱只是喝酒🍺+摸一摸❓ 那你就真的只体验到了冰山一角🥳 摸🍓只是最基础的互动👅 👅氛围到位，🍓互动才是重点🥵 🍓各种互动游戏🍓欢乐不断🍓 包厢里想怎么玩就怎么玩🍓气氛直接拉满😀 😀😀😀😀🌼🩷😀😀😀😀😀 💕兄弟聚会🤩生日小酌🤩下班放松🤩 🔥来这里图的就是一个开心🩷尽兴、放松🥂 来一次🤩你就知道为什么这么多兄弟反复来玩✨ 😂😂😂😂😂😂😂😂😂😂 😱提前订房🏗少排队，🏗早点来选择更多！ ✈️：@sk15010512321 频道：https://t.me/beijingSk888888 双向：@Beijing9998_bot 📞：15028718237 #北京摸摸唱 #北京ktv #北京商k预定
坐标：#北京#丰台区 花名: #林老师（个人服务系老师） 课费：1000p-1800 私信：@linlin202bot 双向: @llsdkt_bot 频道：http://t.me/linlaoshita2026 #详情参见课表
坐标：#北京#十里堡 花名: #美琪儿 课费：600P 私信：@BJjpk 双向: @BJjpkbot 频道：https://t.me/BJjpwnnpd #详情参见课表
📱📱📱📱📱📱📱📱 😆北京商k真空的战袍场😄 ☺️150+长腿佳丽成排等候，战袍开衩到腰，情趣制服:女仆、护士、兔女郎OL随你挑😃😃😃 关键时刻战袍扣子飞，灯光骤暗，只剩那条小内裤在灯影里若隐若现。 💓💓💓你在座位上，就能感受到她的呼吸贴在耳边每一次靠近，专属妈咪带队控场，氛围拉满。 📱 📱 😄😃😄😃😄😄😃😄😄😃😃
坐标：#北京#百子湾 花名: #咪咪 课费：1300P 2200PP 私信：@tiantian68999 频道；https://t.me/tianmimi6868 ❤️❤️；爆乳美娇娘 纯天然 38E豪乳 172cm 轻熟 御姐 服务系 骚货 沉浸式 洗面奶 乳交 👙顶级手感 莞式服务 可外可夜，温柔甜美，热情似火😍🤘👄 #详情参见课表|
Showing the 5 most recent of 5 posts we hold for @bjthb2. 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.
@bjthb2 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.
Citation-graph rank — 1,616,646 of 1,624,174entries 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.
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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“北京探花榜” (@bjthb2), 31,755 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/bjthb2.
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.