Channel
@BD0168
On this record: Growth · Engagement · Posts · Citations · Cite this entry
32,428subscribers
-271 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001689535762 |
|---|---|
| Type | Channel |
| Username | @BD0168 |
| Created | Between 1 December 2021 and 30 April 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 | 15 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/BD0168 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 17:58 | 32,428 | -12 |
| 21 Aug 2026, 07:55 | 32,440 | -3 |
| 20 Aug 2026, 11:12 | 32,443 | -8 |
| 19 Aug 2026, 11:17 | 32,451 | -23 |
| 18 Aug 2026, 11:13 | 32,474 | -22 |
| 17 Aug 2026, 10:05 | 32,496 | -35 |
| 15 Aug 2026, 18:16 | 32,531 | -18 |
| 14 Aug 2026, 03:27 | 32,549 | -38 |
| 12 Aug 2026, 18:55 | 32,587 | -13 |
| 11 Aug 2026, 21:46 | 32,600 | -21 |
| 10 Aug 2026, 22:21 | 32,621 | -23 |
| 9 Aug 2026, 22:12 | 32,644 | -30 |
| 8 Aug 2026, 21:31 | 32,674 | -25 |
| 7 Aug 2026, 12:00 | 32,699 | no change |
| 7 Aug 2026, 11:58 | 32,699 | first reading |
6 posts held, back to 4 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 34 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 29 July 2026 |
|---|---|
| Posts held | 6 (4 July 2026 – 29 July 2026) |
| Views total | 128 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 17:22 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.
⚠️重要通知 尊敬的各大代理 2026年七月已进入倒计时咯，当月负盈利佣金发放的先决条件就是，您的代理线本月达到5名以上的活跃会员且有负盈利才算激活代理线并产生佣金！ 👍 代理后台无需绑定任何信息，做到完全匿名化、佣金USDT结算、无风控、匿名无风险、保障信息安全 新老会员首复存，彩金送不停，复存每日都可领取彩金 😄 如何开发会员 😄 如何维护会员 😄 充提问题 IP限制 😄 简单四招成为代理 😄 代理净盈利额外奖金激励 代理成长等级：场馆费返利 存提手续费返利 额外佣金、发展基金、年终奖 负盈利55%佣金（可享有12个月扶持期） 新代理渠道费报销 (❗️有渠道没费用？别担心，我们给您报销） 💎星空体育 💎开云体育 💎MK体育 💎O D 体育 💎爱 游 戏 💎华 体 会 💎乐鱼体育 💎九游娱乐 💎米兰体育 ➡ 认证品牌 ➡ 极速全面 ➡ 大额无忧 🥰 全网寻找｜SEO｜劫持｜站长…
⚠️重要提醒 佣金审核通过的会在7-15号陆续派发哦，祝各大代理盈利多多💰💰 基础佣金：代理后台-佣金报表-右上角（发佣申请验证） 后台佣金报表中，申请基础佣金LOGO 已出，自行点击申请一下佣金（备注可以不填写） 注：代理扶持期佣金发放政策，分两次发放：1、基础佣金比例30%起，2、扶持佣金比例，不分先后发放。 优先派发要求：完成验证且在当月有5个新增优先派发 ⚠️需要注意：没有在后台验证通过的代理，不派发佣金。 👍 代理后台无需绑定任何信息，做到完全匿名化、佣金USDT结算、无风控、匿名无风险、保障信息安全 新老会员首复存，彩金送不停，复存每日都可领取彩金 😄 如何开发会员 😄 如何维护会员 😄 充提问题 IP限制 😄 简单四招成为代理 😄 代理净盈利额外奖金激励 代理成长等级：场馆费返利 存提手续费返利 额外佣金、发展基金、年终奖 负盈利55%佣金（可享有12个月扶持期） 新代理渠道费报销 (❗️有渠…
🥰 七月活动上新 🅰️负盈利长期55%佣金（客户输100w 👍您拿55w ） ❶ 人头费新增奖励（❗️线红了？别担心，我们给您发工资） ❷ 优质活跃会员和世界杯活跃狂欢活动 ❸ 限时周人头费活动 ❹ 限时体验金活动，体验金充值100送100，最高送888！ ⚠️温馨提示：所有活动务必在后台报名（常规活动）跟（限时活动），一键报名哦‼️ 不报名活动默认不参与当月活动，会导致佣金与人头费、优质会员等活动奖励无法派发 👍 代理后台无需绑定任何信息，做到完全匿名化、佣金USDT结算、无风控、匿名无风险、保障信息安全 新老会员首复存，彩金送不停，复存每日都可领取彩金 😄 如何开发会员 😄 如何维护会员 😄 充提问题 IP限制 😄 简单四招成为代理 😄 代理净盈利额外奖金激励 代理成长等级：场馆费返利 存提手续费返利 额外佣金、发展基金、年终奖 负盈利55%佣金（可享有12个月扶持期） 新代理渠道费报销 (❗️有渠…
开云～七月活动上新
OD～七月活动上新
米兰～七月活动上新
Showing the 6 most recent of 6 posts we hold for @BD0168. 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 — 382,939 of 1,584,142entries 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.
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.
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.
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.
“星空体育【代理部】🔥” (@BD0168), 32,428 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/BD0168.
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.