#GBANNED 群組: 《理想国》每晚10:30直播🔞 (-1001276157022) 執行人: 喵喵喵 對象: 领导 對象UID: 5497660969 時間: 2022-07-14T13:45 原因: 0xCACP 於 1 群組成功。
Signed Sibyl System

Channel
@Bifrost_System
On this record: Growth · Engagement · Posts · Citations · Cite this entry
23subscribers
-1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001446894797 |
|---|---|
| Type | Channel |
| Username | @Bifrost_System |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/Bifrost_System |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 22:38 | 23 | -1 |
| 11 Aug 2026, 11:17 | 24 | no change |
| 10 Aug 2026, 10:02 | 24 | first reading |
20 posts held, back to 14 July 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 20 posts for this entry, the most recent from 14 July 2022. An engagement rate over an empty window would be a number about nothing.
#GBANNED 群組: 《理想国》每晚10:30直播🔞 (-1001276157022) 執行人: 喵喵喵 對象: 领导 對象UID: 5497660969 時間: 2022-07-14T13:45 原因: 0xCACP 於 1 群組成功。
Signed Sibyl System
#GBANNED 群組: 臺北西門町📽感謝安倍首相長年支持臺灣🛍吃喝玩樂來𨑨迌 (-1001291303365) 執行人: 極白熊☀️ 對象: 果酱味奶糖 對象UID: 2090721678 時間: 2022-07-14T13:27 原因: 0xSPAM 0xNSFW 於 1 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 01 (-1001759567896) 執行人: 💛luna🐇good💛 對象: 荣耀代发推广 對象UID: 5104478629 時間: 2022-07-14T13:21 原因: 0xSPAM 於 0 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 01 (-1001759567896) 執行人: 💛luna🐇good💛 對象: nu 對象UID: 5433158887 時間: 2022-07-14T13:19 原因: 0xSPAM 於 0 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 02 (-1001660532762) 執行人: 🇺🇦୧⍤⃝🥚把奈 對象: 三重❤️趴趴 對象UID: 5107953975 時間: 2022-07-14T12:36 原因: 0xSPAM 於 2 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 02 (-1001660532762) 執行人: 社交慵懶卡比瘦 對象: lotodo 對象UID: 5468102166 時間: 2022-07-14T12:27 原因: 0xPRIVATE 0xSPAM 於 0 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 01 (-1001759567896) 執行人: Carmen 對象: 對象UID: 5290384211 時間: 2022-07-14T10:47 原因: 0xSPAM 0xSCAM 於 0 群組成功。
Signed Sibyl System
#GBANNED 群組: 台灣專屬⚜️打屁閒聊18禁 公開群 (-1001521805007) 執行人: 社交慵懶卡比瘦 對象: feng 對象UID: 5424416908 時間: 2022-07-14T09:49 原因: 0xSPAM 於 1 群組成功。
Signed Sibyl System
#GBANNED 群組: 台灣專屬⚜️打屁閒聊18禁 公開群 (-1001521805007) 執行人: 社交慵懶卡比瘦 對象: TPL 對象UID: 5547331721 時間: 2022-07-14T09:49 原因: 0xSPAM 於 1 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 02 (-1001660532762) 執行人: 社交慵懶卡比瘦 對象: Y核机 對象UID: 5495184036 時間: 2022-07-14T09:34 原因: 0xPRIVATE 0xSPAM 於 0 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 02 (-1001660532762) 執行人: 社交慵懶卡比瘦 對象: KДарья 對象UID: 5523412543 時間: 2022-07-14T09:33 原因: 0xPRIVATE 0xSPAM 於 0 群組成功。
Signed Sibyl System
#GBANNED 群組: CID • 01 (-1001759567896) 執行人: 💛luna🐇good💛 對象: K 對象UID: 5311980783 時間: 2022-07-14T08:50 原因: 0xSPAM 0xSCAM 於 0 群組成功。
Signed Sibyl System
Showing the 12 most recent of 20 posts we hold for @Bifrost_System. 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 — 707,271 of 1,624,904entries 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.
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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“Bifrost System - 聯合自動調試診斷修復子系統” (@Bifrost_System), 23 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/Bifrost_System.
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.