最后一次抽奖已经开始

Channel
֍可莉日常֎
@ibilibili
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
47,636subscribers
+701 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001641488543 |
|---|---|
| Type | Channel |
| Username | @ibilibili |
| Description | 可莉分享的Loon资源 Loon的官方群组 @Loon0x00 Loon的三方群组 @LoonCommunity 广告合作请联系 @iKeLeeBot |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ibilibili |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 48% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 08:01 | 47,636 | +96 |
| 16 Sept 2026, 04:16 | 47,540 | +41 |
| 14 Sept 2026, 13:58 | 47,499 | +27 |
| 12 Sept 2026, 23:41 | 47,472 | +36 |
| 11 Sept 2026, 03:41 | 47,436 | +28 |
| 8 Sept 2026, 04:36 | 47,408 | +35 |
| 5 Sept 2026, 03:58 | 47,373 | +33 |
| 3 Sept 2026, 10:47 | 47,340 | +38 |
| 2 Sept 2026, 03:35 | 47,302 | +6 |
| 1 Sept 2026, 00:06 | 47,296 | +18 |
| 31 Aug 2026, 01:37 | 47,278 | +12 |
| 30 Aug 2026, 01:52 | 47,266 | +8 |
| 29 Aug 2026, 03:39 | 47,258 | +3 |
| 28 Aug 2026, 03:05 | 47,255 | +17 |
| 27 Aug 2026, 01:14 | 47,238 | +17 |
| 25 Aug 2026, 22:33 | 47,221 | +10 |
| 24 Aug 2026, 21:45 | 47,211 | +35 |
| 23 Aug 2026, 05:46 | 47,176 | +12 |
| 21 Aug 2026, 19:26 | 47,164 | +18 |
| 20 Aug 2026, 13:25 | 47,146 | first reading |
Engagement
83 posts held, back to 21 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 101 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 23.3%
- avg views ÷ 47,636 subscribers
- Avg views / post
- 11,100
- 40 posts measured
- Reaction rate
- 0.307%
- reactions ÷ views · ER floor
- Posts in window
- 40
- of 83 held
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 September 2026 |
|---|---|
| Posts held | 83 (21 July 2026 – 23 September 2026) |
| Views total | 444,780 |
| Reactions total | 1,365 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 06:06 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.
What this channel posts
- Photos
- 575
- Videos
- 30
- Links
- 469
Lifetime counters from Telegram’s own channel header, read 23 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.
- Video runtime
- 50s
- Average length
- 50s
Measured directly from 1 video 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.
Reaction mix
2,074 reactions across 81 posts, in 30 distinct kinds. The most used accounts for 56.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,172 | 56.5% | |
| 👍 | 398 | 19.2% | |
| 😡 | 122 | 5.88% | |
| 🤣 | 86 | 4.15% | |
| 😁 | 61 | 2.94% | |
| 🌚 | 46 | 2.22% | |
| 👌 | 31 | 1.49% | |
| 💔 | 28 | 1.35% | |
| 🤔 | 26 | 1.25% | |
| 🥰 | 20 | 0.964% | |
| 🤯 | 18 | 0.868% | |
| 👏 | 14 | 0.675% | |
| 🥴 | 11 | 0.53% | |
| 🙈 | 8 | 0.386% | |
| ❤🔥 | 6 | 0.289% | |
| 💅 | 5 | 0.241% | |
| 🤪 | 4 | 0.193% | |
| 🤷♂ | 3 | 0.145% | |
| 🌭 | 2 | 0.096% | |
| 🎃 | 2 | 0.096% | |
| 10 further kinds | 11 | 0.53% |
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 83 of the 83 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 2,081 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 83 most recent posts we hold, published 21 July 2026 to 23 September 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
🌕 AshNet机场 - 月满国庆 · 双节同庆 中秋月圆,国庆同庆。 这个假期,愿山河共圆,也愿每一次连接都稳定顺畅。 🎁 全场在售套餐 · 85 折 🎟 优惠码:月满国庆 🗓 活动时间 9 月 23 日 00:00 — 10 月 8 日 23:59 月满山河,万家同庆。 愿这个假期,有团圆相伴,也有稳定的网络陪伴。 前往购买
❤5
Loon的商店版已推送3.5.1(998)版,务必尽快更新。 务必尽快更新!!! 务必尽快更新!!! 务必尽快更新!!!
👌31👏10❤2
❄️ 吹䨮-云 SnowDrift☁️Cloud 🛡 采用最新协议 VLESS Reality 🏠 全球优质原生 / 家宽 IP 重点部署:美国、日本、香港、台湾 地区家宽(Residential IP)与原生节点,风控极低!后续我们将持续增加更多国家和地区的家宽节点,不断提升您的上网体验! 🎬 全流媒体 & AI 完美解锁 节点支持 Netflix、Disney+、YouTube Premium、HBO Max 等 4K/8K 超高清解锁,无缝访问 ChatGPT / OpenAI,告别封禁与限制! 📱 全平台多设备支持 全面兼容 Windows、macOS、iOS、Android、路由器,支持 Clash、Shadowrocket、Sing-Box 等主流客户端一键导入。 🎁 【新老用户专属福利】 新老用户购买 周期性套餐,结账时输入专属优惠码,即可享受 永久 9 折优惠! 🎟 专属 9 折优惠码: sn…
❤5🤷♀1
🎉 联掌门户去广告 ⭐️ 移除开屏广告、弹窗,移除首页、服务和发现页面无用内容。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 🔗 机场推荐 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin
👍6❤5
1. 重新排版并完善了插件中心的使用规则; 2. 明确了使用插件中心和授权站的用户在发现他人在中国境内平台公开传播或售卖插件时的举报义务。
❤19👍18
老💗婆 ❤️不 💗 在 ❤️家 💗 一💗个 ❤️人 💗寂 ❤️寞 💗 ✈️✈️✈️火☆熱☆勁☆慡☆網☆速☆ 🉐 最低只要 💥8 元/月💥 🛜 IEPL 专线稳定在线 💨 全天 8K 秒开!刷剧看片无压力 🎮 超低延迟,吃鸡、原神统统稳! 🎬 ChatGPT / Netflix 全部解锁! 📦 赠送高达 1PB Emby 影视资源! 🔥 新用户专属 9 折优惠码:ikelee 🔞❤️激情不限流♥️♥️♥️ 🐱点击进来享受 ➡️ 注册入口 🇨🇳官方群组 ➡️ Telegram 群组
🌚3😡3❤1😍1
🌚运动世界校园难搞,去不了广告了
💔28🤣12🌚5🙈3❤2🤷♂1
🎉 马克水印相机去广告 ⭐️ 移除开屏广告,拍摄首页悬浮挂件,侧边栏横幅广告。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 🔗 机场推荐 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin
❤9
❄️ 吹䨮-云 SnowDrift☁️Cloud 🛡 采用最新协议 VLESS Reality 🏠 全球优质原生 / 家宽 IP 重点部署:美国、日本、香港、台湾 地区家宽(Residential IP)与原生节点,风控极低!后续我们将持续增加更多国家和地区的家宽节点,不断提升您的上网体验! 🎬 全流媒体 & AI 完美解锁 节点支持 Netflix、Disney+、YouTube Premium、HBO Max 等 4K/8K 超高清解锁,无缝访问 ChatGPT / OpenAI,告别封禁与限制! 📱 全平台多设备支持 全面兼容 Windows、macOS、iOS、Android、路由器,支持 Clash、Shadowrocket、Sing-Box 等主流客户端一键导入。 🎁 【新老用户专属福利】 新老用户购买 周期性套餐,结账时输入专属优惠码,即可享受 永久 9 折优惠! 🎟 专属 9 折优惠码: sn…
❤10👍2🙉1
ENET今天正式支持了Snell v4/v5/v6 目前所有节点全部支持自由切换SS2022/Trojan/Snell三类代理协议,需在用户中心自行变更。
❤8
抽奖中午已经开始了
❤5
Showing the 12 most recent of 83 posts we hold for @ibilibili. 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.
Posts edited after publishing
@ibilibili edited 5 posts 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.
- First edit seen
- 16 August 2026
- Most recent edit
- 16 September 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@LoonNews · 45,63429 postsLoon Community News
@Loon_Community · 10,65211 postsLoon Tutorial
@LoonTutorial · 3,4692 posts整点猫咪Channel
@GetMoeCats · 4,3971 post🍟 整点薯条: 频道
@GetSomeFriesChannel · 20,0441 postHell Cell 功能教学
@HellCellZC123 · 10,8421 post电报小助手
@dbxzs · 22,1141 postJust PLAY
@demo2099 · 5151 postToMemo Channel
@tomemochannel · 2,2211 post中文资源整合
@zhenghe_fx · 4,5141 postVPS自留地
@zx_vps · 4161 post
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 11 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.
@LoonNews · 45,63499 postsLoon Community News
@Loon_Community · 10,65258 postsHell Cell 功能教学
@HellCellZC123 · 10,8425 posts曙光云知识库
@shuguangcloudku · 132 postsNaruto 频道推荐 👍👍👍
@AChansp · 23,5741 post不限时机场
@buxianshi · 521 post谷雨观察🌍
@guyuObservation · 3,8981 postLoon Tutorial
@LoonTutorial · 3,4691 post猫群讯息频道
@maoqunpd · 8081 post🚀整点火箭
@Shadowrocket_Helper_Unofficial · 161 postVPS自留地
@zx_vps · 4161 post
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.
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.
@LoonNews · 45,634#1
@NobyDa · 63,380#2
@LUCYChannel_1024 · 7,129#3
@GitCube · 10,726#4
@Aa28413761 · 26,154#5
@zhetengsha · 49,269#6
@zaihuapd · 282,472#7
@GodlyNews1 · 68,855#8
@GetMoeCats · 4,397#9
@FutureEcho_Notice · 7,220#10
@cool_scripts · 16,278#11
@gebaopiCloud · 101,135#12
@ibeta_channel · 13,549#13
@AppleNuts · 37,006#14
@HellCellZC123 · 10,842#15
@inaisi · 13,204#16
@NewlearnerChannel · 67,412#17
@XiaoMaoScript · 3,129#18
@rocCHL · 36,047#19
@FlClash · 46,371#20
@guozhiapp · 22,559#21
@DNSPODT · 71,856#22
@Z_Turns · 5,712#23
@scriptableJS · 11,092#24
@st77eve · 5,793#25
@deb_dylib · 22,152#26
@ffqchannel · 62,201#27
@ioskk · 49,749#28
@Quantumultxxxx · 20,872#29
@jctest6666 · 10,326#30
@SurgeTestFlightFeed · 12,910#31
@xhqcankao · 163,238#32
@tkv_ktv · 2,491#33
@testflights · 10,674#34
@tnews365 · 164,267#35
@VPN_Police · 8,155#36
@jngchannel · 16,956#37
@h5683577 · 6,552#38
@yamby_release · 36,793#39
@surfboardnews · 28,438#40
Read from Telegram’s recommendation API, most recently 14 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.
@guozhiapp · 22,559
Telegram ranks this channel #1 of 25 here — alongside 24 others — read 20 September 2026
@deb_dylib · 22,152
Telegram ranks this channel #2 of 23 here — alongside 22 others — read 21 September 2026
@ae86_dao · 25,526
Telegram ranks this channel #3 of 25 here — alongside 24 others — read 14 September 2026
@odysseyplus · 24,933
Telegram ranks this channel #14 of 29 here — alongside 28 others — read 15 September 2026
@cheapairport_channel · 24,910
Telegram ranks this channel #23 of 30 here — alongside 29 others — read 15 September 2026
@freeVPNjd · 23,009
Telegram ranks this channel #28 of 31 here — alongside 30 others — read 19 September 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists 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.
“֍可莉日常֎” (@ibilibili), 47,636 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ibilibili.
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.