Telegram RegisterThe public register of Telegram
Telegram profile photo for 哔哩漫游

Channel

哔哩漫游

@biliroaming

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

56,222subscribers

+419 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001495256052
TypeChannel
Username@biliroaming
Description评论需要先进群。不然会被禁言。
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/biliroaming

Topic

Gaming — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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 why it has no browse page of its own yet.

Growth

55,80356,22256,012.57 August 2026 — 55,803 subscribers7 August 2026 — 55,803 subscribers8 August 2026 — 55,807 subscribers9 August 2026 — 55,820 subscribers10 August 2026 — 55,834 subscribers11 August 2026 — 55,840 subscribers12 August 2026 — 55,841 subscribers13 August 2026 — 55,840 subscribers14 August 2026 — 55,855 subscribers15 August 2026 — 55,881 subscribers17 August 2026 — 55,892 subscribers18 August 2026 — 55,902 subscribers19 August 2026 — 55,904 subscribers20 August 2026 — 55,923 subscribers21 August 2026 — 55,929 subscribers23 August 2026 — 55,944 subscribers24 August 2026 — 55,954 subscribers25 August 2026 — 55,975 subscribers26 August 2026 — 55,996 subscribers27 August 2026 — 56,010 subscribers28 August 2026 — 56,028 subscribers29 August 2026 — 56,053 subscribers30 August 2026 — 56,064 subscribers31 August 2026 — 56,068 subscribers1 September 2026 — 56,108 subscribers2 September 2026 — 56,115 subscribers4 September 2026 — 56,138 subscribers6 September 2026 — 56,158 subscribers10 September 2026 — 56,171 subscribers12 September 2026 — 56,179 subscribers14 September 2026 — 56,195 subscribers15 September 2026 — 56,209 subscribers18 September 2026 — 56,222 subscribers7 August 202618 September 2026
33 measurements spanning 42 days, net +419. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 55,740–56,285 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
18 Sept 2026, 00:5756,222+13
15 Sept 2026, 19:4256,209+14
14 Sept 2026, 01:0056,195+16
12 Sept 2026, 09:2156,179+8
10 Sept 2026, 07:3756,171+13
6 Sept 2026, 22:3556,158+20
4 Sept 2026, 11:1556,138+23
2 Sept 2026, 20:1456,115+7
1 Sept 2026, 19:4856,108+40
31 Aug 2026, 19:0556,068+4
30 Aug 2026, 15:4456,064+11
29 Aug 2026, 17:5656,053+25
28 Aug 2026, 20:1456,028+18
27 Aug 2026, 17:0356,010+14
26 Aug 2026, 16:2455,996+21
25 Aug 2026, 18:4855,975+21
24 Aug 2026, 16:0355,954+10
23 Aug 2026, 03:2455,944+15
21 Aug 2026, 13:5755,929+6
20 Aug 2026, 15:1855,923first reading

Engagement

22 posts held, back to 5 August 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 105 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 22 posts for this entry, the most recent from 23 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
21
Videos
4
Links
991

Lifetime counters from Telegram’s own channel header, read 27 September 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.

Reaction mix

7,150 reactions across 22 posts, in 34 distinct kinds. The most used accounts for 23.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😭1,67523.4%
😱1,36719.1%
❤1,06014.8%
👍6469.03%
😁5387.52%
🤡4836.76%
🥰4556.36%
🤣2183.05%
💩2012.81%
🤯831.16%
😨550.769%
🖕520.727%
🎉400.559%
🤩330.462%
👎310.434%
🍾250.35%
🤨240.336%
👏220.308%
🤬210.294%
🗿170.238%
14 further kinds1041.45%

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 22 of the 22 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 7,150 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 5 August 2025 to 23 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

23 Aug 2026, 02:44 UTC≈25,200 views79 reactionsread 27 September 2026

https://play.google.com/store/apps/details?id=com.bilibili.app.in

👍61❤18

23 Aug 2026, 02:44 UTC≈25,200 views156 reactionsread 27 September 2026

我个人观察来看 应该是叔叔把东南亚的番剧搬到主站了 打算把主站国际化 于是把白板捡回来了 陆版搜不到这些番剧,仅此而已,即便挂节点 白板挂东南亚IP能搜到 然后链接能跳给陆版 陆版能播 甚至跳piliplus 绝对不可能有.tv资源的端( 只要IP正确都能播放 因为都是在主站 部分即便会员限定 会员也是通用的

👍137❤19

6 Jul 2026, 14:25 UTC≈79,000 views1,089 reactionsread 27 September 2026
Photo

隔壁也收到了

😭910🤣51🤩30😱21🤬20❤18🤮15💊8

6 Jul 2026, 02:58 UTC≈206,000 views1,544 reactionsread 27 September 2026
Photo

https://www.ithome.com/0/973/202.htm

😱1,170💩192🖕52🤯45🤡32😁17😢17🎉9

18 Jun 2026, 14:31 UTC≈80,200 views173 reactionsread 27 September 2026
File

New push to github! fix: 启动卡顿及getAccessKey查找失效 (#1717) initHookInfo 的 biliAccounts 块依赖 "initFacial enter" 字符串锚点定位 getAccessKey,该锚点在8.98.0被移除导致查找失败;readHookInfo 缓存校验中的 getAccessKey 非空条件又会使该失败状态触发每次启动全量重扫死循环(约2.6s卡顿)。 - readHookInfo: 移除 getAccessKey 非空缓存校验,消除死循环 - initHookInfo: biliAccounts 块在锚点反推失败时回退到 declaredMethods 按签名/方法名查找,兼容8.98.0(方法名未混淆);保留原调用图反推以兼容 方法名被混淆的历史版本 fix #1716 by xueshiji See commit detail here Sn…

❤140🥰21👍9👏2😇1

12 Jun 2026, 15:50 UTC≈77,300 views139 reactionsread 27 September 2026
File

New push to github! feat(video): 添加视频广告跳过功能 (#1701) 一个简单的跳过视频广告功能,参考BilibiliSponsorBlock实现 by cja See commit detail here Snapshot apk is attached (unsupported by TAICHI)

🥰92❤19😭14🎉6👍2💯2🤯2🏆1

12 Jun 2026, 11:35 UTC≈67,900 views69 reactionsread 27 September 2026
File

New push to github! 修复8.97.0+启动时崩溃 (#1714) 注意:采用claude code进行辅助分析和构建,所有代码和设计经过人工审核 API版本:100 测试版本:8.46.0 / 8.98.0 注意:使用较新的B站版本可能因为部分功能未适配导致部分功能失效 - 修复了因 Kotlin 接口属性编译为 getter 方法而非字段获取 descriptor 的值时抛出 NoSuchFieldError - 修复了Compose 开屏自定义启动图因 ComposeView 禁止 addView 失效 - 新增了清除hook缓存的功能,解决因版本号长期未变更导致hook info缓存部分时候未能按预期情况失效的问题 by loliconRoot See commit detail here Snapshot apk is attached (unsupported by TAICHI)

🥰46❤15👍8

12 Jun 2026, 04:03 UTC≈54,200 views91 reactionsread 27 September 2026
File

New push to github! 修复8.97.0及以上版本崩溃问题,同时修复部分失效功能 (#1713) 注意:采用claude code进行辅助分析和构建,所有代码和设计经过人工审核 API版本:100 测试版本:8.46.0 / 8.97.0 / 8.98.0 注意:使用较新的B站版本可能因为部分功能未适配导致部分功能失效 - 修复了多个导致8.97.0及以上版本崩溃的问题 - 修复了8.97.0版本设置按钮未能正确显的问题 - 进一步修复了开屏广告屏蔽功能 - 修复了部分情况下自定义开屏功能失效 - 修复了av号显示功能在8.97.0版本失效 API版本101的功能更新将在之后进行 by loliconRoot See commit detail here Snapshot apk is attached (unsupported by TAICHI)

❤61🥰18👍11👏1

9 Jun 2026, 14:07 UTC≈43,400 views147 reactionsread 27 September 2026
File

New push to github! 尝试修复开屏广告跳过功能 (#1708) 注意:采用claude code进行辅助分析和构建,所有代码和设计经过人工审核 测试版本:8.46.0 / 8.95.0 已确认功能可以正常运行,确认成功清除拉取的信息,所有调试日志代码已移除 开屏广告的数据从FastJSON迁移到了Gson,导致原有Hook失效。所以添加了一个GsonHook处理相关数据。 tv.danmaku.bili.ui.splash.SplashData -> tv.danmaku.bili.splash.ad.model.SplashListResponse by MRKT_ROOT See commit detail here Snapshot apk is attached (unsupported by TAICHI)

👍110🥰24❤11😁2

24 May 2026, 05:10 UTC≈51,100 views1,026 reactionsread 27 September 2026
Photo

今天是可能倒闭但绝不变质的十周年纪念日

😁456🤡335🤣167🍾25❤14🤔11👍7🥰5

17 Apr 2026, 16:42 UTC≈75,100 views1,033 reactionsread 27 September 2026

白菜怎么毕业了😭

😭751🤡111😨55🤨24🎉19🗿17👎15😱15

20 Mar 2026, 13:49 UTC≈92,900 views184 reactionsread 27 September 2026
File

New push to github! Branch: feat/api-101 This version is ONLY FOR LSPosed-it (7601 or higher) or frameworks supporting Xposed API 101 fix: CustomThemeHook minor changes for CopyHook by U29kaXVt See commit detail here Snapshot apk is attached

😱88👍41❤37🥰10👎5🤯3

Showing the 12 most recent of 22 posts we hold for @biliroaming. 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.

Forward network

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.

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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

QAuxiliary CI Builds
@QAuxiliary_CI · 19,541
#1
Bilibili Android Apk w/ HD
@bilibili_apk · 4,074
#2
LibChecker CI
@libchecker_ci · 3,485
#3
TSBattery CI Builds
@TSBattery_CI · 3,599
#4
NPatch
@NPatch · 19,080
#5
LSPosed
@LSPosed · 194,124
#6
FlClash Channel
@FlClash · 47,123
#7
HyperCeiler | Canary Test
@cemiuiler_canary · 19,046
#8
在花🎗️科技圈
@zaihuapd · 283,183
#9
Nagram Tips
@NagramTips · 46,239
#10
Voyager HyperOS Update
@VoyagerMIUIUpdate · 21,528
#11
XiReiki
@xiayinlily · 2,863
#12
Vie APKs
@Kawaii_V · 248
#13
InstallerX
@InstallerX · 8,678
#14
Arch Linux Updates
@archlinuxcn_updates · 720
#15
Hysteria Releases
@hysteria_releases · 9,833
#16
池塘的踢寄空间
@chitang233_channel · 563
#17
QAuxiliary
@QAuxiliary · 44,820
#18
Kimmy's 公开备忘录
@KimmyXYC_Soliloquize · 1,535
#19
FunProject
@QToolCI · 49,485
#20
企业级欢乐花园
@MaterialDesign3 · 9,185
#21
U.M.R Has Something to Record🍥🛠
@umr_has_something_to_record · 492
#22
康娜酱酱酱
@K0bayashi_Kanna · 3,271 (as read 12 September 2026)
#23
QQ Updates
@QQUpdates · 10,203
#24
风向旗参考快讯
@xhqcankao · 163,238
#25
LoopDNS资讯播报
@DNSPODT · 72,064
#26
哔哩哔哩 表情/装扮 存档
@Bilibili_skin · 12,949
#27
亚托莉世界第一可爱
@atri0828 · 2,547
#28
LiFePO4:沙雕吐槽
@lifepofour · 2,209
#29
炸虾🍤
@zhaxia_cn · 12,550
#30
QNotified
@QNotified · 6,745
#31
WeChatJava
@WeChatJava · 2,053
#32
盐酸乙酰胆碱
@teb1e · 525
#33
Yet Another Public Notification Channel
@yapnc · 7,517
#34
Telegram Info 中文
@tginfocn · 5,754
#35
橘橘橘子汁 & 🍊
@microblock_pub · 15,261
#36
YunJava
@YunJava · 4,562
#37
nmBot 频道
@nmbotchannel · 33,754
#38
QQ/TIM Update Log
@qq_updatelog · 6,797
#39
蓝点网订阅频道
@landiansub · 45,199
#40
卖报社
@MaiTungNews · 622
#41
柒柒的鱼骨头
@Sandrone0721 · 1,102
#42
Yamby Release
@yamby_release · 36,854
#43
Nagram
@nagram_channel · 68,755
#44
爱玩机工具箱(文件/通知)
@aiwanji · 8,491
#45
AdClose Official
@AdClose · 12,205
#46
Capoo Stickers
@Capoo_Stickers · 11,382
#47
Foolish TraceWind
@FoolishTraceWind · 16,632
#48
アニメ新番組 Ch
@bangumi_online_ch · 5,124
#49
轻小说仓库
@LightNovels_Collection · 3,106
#50

Read from Telegram’s recommendation API, most recently 12 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

QAuxiliary
@QAuxiliary · 44,820
Telegram ranks this channel #34 of 58 here — alongside 57 others — read 12 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“哔哩漫游” (@biliroaming), 56,222 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/biliroaming.

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.