Photo, posted without a caption
🤡36🤔13🤨7💊6🤣2👍1👎1

Channel
@Shirai_Kurokochan
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,501subscribers
+332 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003872476779 |
|---|---|
| Type | Channel |
| Username | @Shirai_Kurokochan |
| Created | Between 1 February 2026 and 25 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Shirai_Kurokochan |
Gaming — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 16:36 | 1,501 | +86 |
| 15 Sept 2026, 01:00 | 1,415 | +6 |
| 11 Sept 2026, 11:59 | 1,409 | +62 |
| 7 Sept 2026, 02:38 | 1,347 | -5 |
| 2 Sept 2026, 17:17 | 1,352 | +2 |
| 30 Aug 2026, 06:36 | 1,350 | +1 |
| 27 Aug 2026, 06:04 | 1,349 | +11 |
| 23 Aug 2026, 20:47 | 1,338 | +3 |
| 19 Aug 2026, 20:21 | 1,335 | +14 |
| 16 Aug 2026, 20:33 | 1,321 | +55 |
| 13 Aug 2026, 02:37 | 1,266 | +43 |
| 9 Aug 2026, 17:02 | 1,223 | +44 |
| 6 Aug 2026, 15:23 | 1,179 | +10 |
| 6 Aug 2026, 12:02 | 1,169 | no change |
| 6 Aug 2026, 10:30 | 1,169 | first reading |
20 posts held, back to 25 June 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 1 page 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
1,122 reactions across 20 posts, in 30 distinct kinds. The most used accounts for 37.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 422 | 37.6% | |
| ❤ | 143 | 12.7% | |
| 🤣 | 131 | 11.7% | |
| 😭 | 102 | 9.09% | |
| 🔥 | 44 | 3.92% | |
| 😱 | 43 | 3.83% | |
| 👎 | 35 | 3.12% | |
| ❤🔥 | 31 | 2.76% | |
| 🕊 | 31 | 2.76% | |
| 😨 | 19 | 1.69% | |
| 🤔 | 15 | 1.34% | |
| 😁 | 14 | 1.25% | |
| 👍 | 13 | 1.16% | |
| 🤨 | 13 | 1.16% | |
| 👀 | 10 | 0.891% | |
| 💩 | 8 | 0.713% | |
| 💊 | 7 | 0.624% | |
| ✍ | 4 | 0.357% | |
| 💔 | 4 | 0.357% | |
| 🤓 | 4 | 0.357% | |
| 10 further kinds | 29 | 2.58% |
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 20 of the 20 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 1,122 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 25 June 2026 to 6 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.
Photo, posted without a caption
🤡36🤔13🤨7💊6🤣2👍1👎1
如果您对未来会实装的角色抱有期待,我可以负责任确保真实的对您说: 潘塔罗涅,皮耶罗,普契涅拉,卡皮塔诺,艾莉丝,若娜瓦,大家最爱编的萍姐姐,以上在7.Ⅹ大版本内都不会实装。 若娜瓦和潘塔罗涅会死在至冬的剧情中。 钟离是冰之女皇弑杀天理计划中的关键。 If you hold expectations for characters being playable in the future, I can responsibly and truthfully assure you: Pantalone, Pierro, Pulcinella, Capitano, Alice, Ronova, and Madam Ping—the one everyone loves to make up rumors about—will not be playable within the 7.X versions. Ronova and P…
🤡146😭51🤣18❤11💔4🤪4👏1😁1
若娜瓦相关的剧情里会出现寒天之钉 Skyfrost Nail will appear in the storyline related to Ronova.
❤25🤡14😁8
关于若娜瓦 7.1版本我们就要打若娜瓦,跟她永别了。 若娜瓦攻击了派蒙之后,招致了致命的制裁。 因为若娜瓦要颠覆世界,之后版本七神都来了。 刚见面就要说再见了👋🏻如果你希望她未来还有机会复活,可以在各个平台多表达表达,兴许人气足够未来还有可能呢?反正现在是寄了 About Ronova In Version 7.1, we'll be fighting Ronova and saying our final goodbyes to her. After attacking Paimon, Ronova brought a fatal divine judgment upon herself. Because she sought to overturn the world, all the Seven Archons will be making an appearance in the upcoming versions. …
🤡97🕊31🤣16😭15❤10👍6🌭3🥰2
Very late Snezhnaya actually -DK2
🤡9❤3🎄1🤣1
戴因斯雷布将会在7.X大版本内进池自机 Dainsleif will be playable in version 7.X ▌「拾枝者」·戴因斯雷布 未来与过去的结点 ===================== 「原初逆转了毁灭,天空之岛焚烧了大地之国。白垩追逐着黄金,赤月对黑日复仇。未来拯救过去,年长者与年幼者同血相残。——这是世间回环的命运。戴因,对你来说,那缕金发又是什么呢?必须杀死的人,还是忏悔的对象?」 ——自称通晓命运之人
🤣94😱38🔥9❤8👎7🤨2😁2🍾1
外面吵女皇定位好像吵的很欢,但我的来源是说女皇可以进木偶队伍
❤12✍4🤨4🔥2😁2
关于诺伊 亥珀波瑞亚时代的人,与深廊套里的记述者文明有交集 About Noy A person from the Hyperborean era, He has connections to the Scribe civilization mentioned in the Deep Galleries.
❤🔥31❤2🔥2💩1🤔1
关于达妮卡 🦈女仆,五星不是四星,剧情出场比较靠后 About Danica She is the shark maid. She's a 5-star character, not a 4-star. She appears relatively late in the story.
🔥25👎22👏1
We will have a fight with Ronova Thank you DK2 for the info
❤7👏1
好好珍惜吧,看一眼少一眼了 Cherish her while we can
😭18🤬2❤1🤡1
Photo, posted without a caption
❤7😭6🤡2🗿1🤬1😱1
Showing the 12 most recent of 20 posts we hold for @Shirai_Kurokochan. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“白井黒子” (@Shirai_Kurokochan), 1,501 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Shirai_Kurokochan.
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.