【星际穿越】 新增4个🇸🇬新加坡节点 刷新订阅就能用 官网: xingji.win 探针: 点击查看
👍5🤬2👀1👌1

Channel
@BQ_01
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
13,413subscribers
+1,819 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001628126132 |
|---|---|
| Type | Channel |
| Username | @BQ_01 |
| Description | 放点好东西,经常发福利抽奖俗称白嫖小仓库。 频道自运营机场:星际穿越 官网:xingji.win 发布页:vip.星际.lol 群聊:https://t.me/BQ_02 |
| 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 | 10 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/BQ_01 |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 57% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 06:29 | 13,413 | +37 |
| 8 Nov 2026, 17:57 | 13,376 | +78 |
| 7 Nov 2026, 11:55 | 13,298 | +30 |
| 6 Nov 2026, 13:26 | 13,268 | +16 |
| 5 Nov 2026, 10:29 | 13,252 | +31 |
| 4 Nov 2026, 11:05 | 13,221 | +42 |
| 3 Nov 2026, 07:35 | 13,179 | +16 |
| 2 Nov 2026, 09:36 | 13,163 | +41 |
| 1 Nov 2026, 09:55 | 13,122 | +22 |
| 31 Oct 2026, 13:06 | 13,100 | +25 |
| 30 Oct 2026, 10:56 | 13,075 | +27 |
| 29 Oct 2026, 08:21 | 13,048 | +4 |
| 28 Oct 2026, 06:00 | 13,044 | +22 |
| 27 Oct 2026, 07:09 | 13,022 | +10 |
| 26 Oct 2026, 05:20 | 13,012 | +15 |
| 25 Oct 2026, 02:38 | 12,997 | +18 |
| 23 Oct 2026, 23:16 | 12,979 | +32 |
| 23 Oct 2026, 00:45 | 12,947 | +12 |
| 22 Oct 2026, 00:51 | 12,935 | +21 |
| 20 Oct 2026, 18:25 | 12,914 | first reading |
60 posts held, back to 23 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 66 pages of 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 10 November 2026 |
|---|---|
| Posts held | 60 (23 December 2025 – 10 November 2026) |
| Views total | 51,002 |
| Reactions total | 100 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 09:13 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.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
238 reactions across 49 posts, in 12 distinct kinds. The most used accounts for 47.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 112 | 47.1% | |
| ❤ | 102 | 42.9% | |
| 👏 | 6 | 2.52% | |
| 🤡 | 4 | 1.68% | |
| 😈 | 3 | 1.26% | |
| 🙏 | 3 | 1.26% | |
| 😍 | 2 | 0.84% | |
| 🤬 | 2 | 0.84% | |
| 👀 | 1 | 0.42% | |
| 👌 | 1 | 0.42% | |
| 😱 | 1 | 0.42% | |
| 🥰 | 1 | 0.42% |
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 53 of the 60 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 238 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 60 most recent posts we hold, published 23 December 2025 to 10 November 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.
Telegram’s own ‘edited’ marker: 9 of 18 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
【星际穿越】 新增4个🇸🇬新加坡节点 刷新订阅就能用 官网: xingji.win 探针: 点击查看
👍5🤬2👀1👌1
此消息由星际穿越员工「快米狗」发布 🎁 抽奖 奖品:超快套餐一个月 × 3 已参与:99 人 开奖:已开奖 中奖:3 / 3 参与方式 在群内发送「抽奖抽着玩」 参与条件 已加入官方群 · 已关注官方频道 · 已绑定星际账号 @XingJiJiChang_Bot 活动说明 已有超快套餐中奖自动续费30天,没有有效套餐直接开通超快30天,其他有效套餐中奖自动增加3.99元账户余额。 中奖用户 1. @llluoheng 2. @spp9527 3. kitty hello 报名和开奖时都会再次验证参与资格。
👍6❤1
#频道互推 #群组推荐 朱颜别镜 | 妹子图 | 美女图 SCP || 每日免费节点 sfw的二次元萌妹美图频道 免费高速订阅节点 极客分享2.0 [震撼回归] 精选小说音乐 分享推荐 热门短剧每日分享 Magazine-期刊杂志 二次元轻小说书屋 电报频道索引 互推:@miaomiao333bot
❤1
【星际穿越索引】 发布页: vip.xingji.win vip.星际.lol xjcy.pages.dev (备用发布页) 官网: xingji.win (直连可访问) 星际.lol (需要代理访问) www.星际.lol (需要代理访问) 小火箭共享账号 丨 开自己的机场 节点探针 丨 藏宝阁 丨 社区 丨 群聊
👍4❤2
昨天有内鬼泄露订阅导致节点IP在短时间内频繁被墙 已针对特殊指纹和特征上线 【反内鬼系统】 封禁一批账户订阅后恢复正常,稳定运行,没有再出现IP被墙的情况。 如果有误封请发工单+群聊内反馈,复核后解封并给予补偿。 为了更稳定流畅 今天会全面升级【反内鬼系统】2.0 将全面接入 Claude Opus 5.5 超高 GPT 6.1 Terra极高 DeepSeek-V4.1flash max 多个大模型协同全天24小时监控任何异常 不再是昨天第一版仓促上线的固定的系统识别版本 有误封发工单解封并给予补偿 (误封概率极小)
👍10❤3
新功能藏宝阁上线 不定期上架一些,超级折扣价,限量库存的,不一样的好东西。 xingji.win 入口在官网 购买订阅页面 【藏宝阁】按钮进入 藏宝阁直达入口点这里
👍3
节点许愿池 想用什么地区的节点,可以去许愿投票 点击这里投票
👍3
【星际穿越】 新增4个不限速,移动用了速度快到直呼受不了的节点 两个🇯🇵日本女优节点给大家上 两个🇸🇬新加坡大富豪节点 超快套餐刷新订阅就能看到 官网: xingji.win
👍4❤1
【星际穿越】 新增两个🇸🇬新加坡0.1倍率节点 有50Mbps限速 超快套餐刷新订阅就能看到 官网: xingji.win
❤2
【星际穿越】 超快套餐 上线🇺🇸美国家宽节点 AI专用 解锁一切 此节点高倍率 禁流媒体 (AI用不了多少流量,看流媒体可以用0倍率节点♾️无限用不扣流量) 官网: xingji.win
❤5👍1
【星际穿越】 新增两个超快不限时套餐 包含超快月付套餐的部分节点 200G / 1T 流量可选 官网: xingji.win
👍6
File, posted without a caption
👍3
Showing the 12 most recent of 60 posts we hold for @BQ_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.
@BQ_01 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.
We recorded 2 posts on @BQ_01 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 2 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.
@BQ_01 named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“白嫖小仓库丨星际穿越” (@BQ_01), 13,413 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/BQ_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.