Channel
@bb_nb7
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,121subscribers
-47 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001852523744 |
|---|---|
| Type | Channel |
| Username | @bb_nb7 |
| 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 | 22 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/bb_nb7 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 00:29 | 2,121 | -3 |
| 18 Aug 2026, 17:13 | 2,124 | -18 |
| 15 Aug 2026, 07:42 | 2,142 | -8 |
| 11 Aug 2026, 19:16 | 2,150 | -14 |
| 8 Aug 2026, 08:48 | 2,164 | -4 |
| 7 Aug 2026, 10:16 | 2,168 | no change |
| 7 Aug 2026, 10:04 | 2,168 | first reading |
10 posts held, back to 23 July 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 2 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 6 August 2026 |
|---|---|
| Posts held | 10 (23 July 2026 – 6 August 2026) |
| Views total | 425 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:53 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.
#频道互推 #相似推荐 ------------------------------ 📢 盯潮裸聊选妃 📢 小森林裸聊反差频道 📢 奈奈1v1裸聊和原味 📢 武汉摸摸唱/裸嗨/KTV/mmc/尺度场 📢 裸聊伎町选妃 📢 书瑶认证巨乳福利姬（ 1V1 裸聊 举牌） 📢 小蟑螂的小窝 📢 裸聊颖儿1V1视频色色 📢 海南怡情汇顶流老师公开榜🅢 📢 萌萌COS💋💋大本营 ------------------------------ ☁️ 互推入口：@sooo
Signed SOSO搜搜
Photo, posted without a caption
Signed 张梦涵
⭐梦涵团队全项目总汇⭐ 👤点击蓝色字体加入对应频道 🔎通知频道 🔎安卓项目反馈频道 🔎iOS项目反馈频道 ⚔️项目合作咨询联系 @zmh0102
Signed 张梦涵
用户反馈即将封神
Signed 张梦涵
反馈
Signed 张梦涵
新项目UN零售650周 全自动算法解密 永不回朔集体 漏打自瞄
Signed 张梦涵
⭐梦涵团队全项目总汇⭐ 👤点击蓝色字体加入对应频道 🔎通知频道 🔎安卓项目反馈频道 🔎iOS项目反馈频道 ⚔️项目合作咨询联系 @zmh0102
Signed 张梦涵
封神是不正常的⚔️
Signed 张梦涵
⭐梦涵团队全项目总汇⭐ 👤点击蓝色字体加入对应频道 🔎通知频道 🔎安卓项目反馈频道 🔎iOS项目反馈频道 ⚔️项目合作咨询联系 @zmh0102
Signed 张梦涵
几天不打又涨了kd
Signed 张梦涵
Showing the 10 most recent of 10 posts we hold for @bb_nb7. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“梦涵团队【pc/端游】无畏契约-三角洲-穿越火线-和平精英-王者荣耀-全网各大游戏外挂 · 游戏” (@bb_nb7), 2,121 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/bb_nb7.
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.