https://www.bilibili.com/video/BV1QZ3X6YES8/
🥰4

Channel
@KUNGalgameChannel
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,388subscribers
+115 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001835196897 |
|---|---|
| Type | Channel |
| Username | @KUNGalgameChannel |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 20 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 20 November 2026 |
| On Telegram | t.me/KUNGalgameChannel |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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 |
|---|---|---|
| 20 Nov 2026, 09:18 | 1,388 | +6 |
| 15 Nov 2026, 13:09 | 1,382 | +7 |
| 10 Nov 2026, 07:19 | 1,375 | +6 |
| 6 Nov 2026, 21:04 | 1,369 | +5 |
| 3 Nov 2026, 15:57 | 1,364 | +8 |
| 31 Oct 2026, 16:17 | 1,356 | +5 |
| 28 Oct 2026, 06:00 | 1,351 | +4 |
| 22 Oct 2026, 00:06 | 1,347 | +1 |
| 18 Oct 2026, 08:28 | 1,346 | +2 |
| 12 Oct 2026, 12:04 | 1,344 | +12 |
| 5 Oct 2026, 15:37 | 1,332 | +4 |
| 28 Sept 2026, 01:57 | 1,328 | +10 |
| 15 Sept 2026, 08:16 | 1,318 | +1 |
| 11 Sept 2026, 07:59 | 1,317 | +7 |
| 6 Sept 2026, 17:18 | 1,310 | +1 |
| 2 Sept 2026, 12:34 | 1,309 | +7 |
| 30 Aug 2026, 03:05 | 1,302 | +4 |
| 27 Aug 2026, 04:08 | 1,298 | +2 |
| 24 Aug 2026, 10:54 | 1,296 | +8 |
| 20 Aug 2026, 13:38 | 1,288 | first reading |
12 posts held, back to 2 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 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 12 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
279 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 52.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 145 | 52.0% | |
| ❤ | 36 | 12.9% | |
| 😭 | 36 | 12.9% | |
| 👏 | 21 | 7.53% | |
| 😁 | 11 | 3.94% | |
| 👍 | 10 | 3.58% | |
| ⚡ | 8 | 2.87% | |
| 😱 | 6 | 2.15% | |
| 🤣 | 4 | 1.43% | |
| 🤯 | 2 | 0.717% |
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 12 of the 12 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 279 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 2 December 2025 to 2 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.
https://www.bilibili.com/video/BV1QZ3X6YES8/
🥰4
一看就知道是我们群友会做的
🥰5😁2❤1🤯1
为什么没看到群友,严肃批评!
🤣4😁2🥰1
四年啊!!!!等了整整四年!!!我终于拿下了梦寐以求的 kun.moe !!!现在我正式宣布 鲲 / KUN 成为一个品牌
🥰39👏20❤3
窝这个月又发现一位非常成熟的熟女!!!!! https://x.com/Harvest_Teacher/status/2068299063217504654
🥰17⚡8❤2👏1🤯1
鲲 Galgame 补丁 & 论坛 可能会维护半天或者一天 后端代码和部署结构重构太大了,莲这孩子忙不过来,维护时间未知,快去夸夸她吧 莲这孩子简直就是全栈大师,乌蒙地插吃高手,脚踩 n8n 手撕 k8s kungal.com / moyu.moe
🥰19
群友不会电脑也中病毒了吧,我懂我都懂
❤18
https://www.youtube.com/watch?v=r5n_5zbyik4 她们都是年满 18 岁成熟的孩子,你可以称呼她们为熟女,她们的共同特点就是有一对人人都羡慕的巨乳
🥰9😱6❤2
https://www.soft.moe/topic/vn-story-demo 群友来试试在网页中玩自己写的 Galgame
❤1
这简直就是我
🥰21😁4👍2
这是我这个月见过最性感的熟女!!!
🥰26👍8❤4😁3
这就是值得我爱一辈子的人啊,呜呜呜呜呜呜呜呜呜呜呜!!我好想被爱啊😭
😭36❤5🥰4
Showing the 12 most recent of 12 posts we hold for @KUNGalgameChannel. 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.
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 20 November 2026 — this entry's latest reading, not the date you are reading this.
“鲲 Galgame 频道” (@KUNGalgameChannel), 1,388 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/KUNGalgameChannel.
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.