新年快乐! 恭喜五位幸运跨年人
😍6

Channel
@kamiyanoc
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
582subscribers
-24 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001822329053 |
|---|---|
| Type | Channel |
| Username | @kamiyanoc |
| 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 | 5 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/kamiyanoc |
Giveaways & airdrops — 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 21 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 23:16 | 582 | -3 |
| 25 Sept 2026, 12:37 | 585 | -6 |
| 13 Sept 2026, 20:19 | 591 | -2 |
| 6 Sept 2026, 21:15 | 593 | -3 |
| 29 Aug 2026, 07:27 | 596 | -3 |
| 23 Aug 2026, 03:57 | 599 | -2 |
| 15 Aug 2026, 03:34 | 601 | -4 |
| 7 Aug 2026, 17:28 | 605 | -1 |
| 7 Aug 2026, 10:17 | 606 | no change |
| 7 Aug 2026, 09:18 | 606 | first reading |
20 posts held, back to 2 November 2023 — 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 31 December 2023. An engagement rate over an empty window would be a number about nothing.
131 reactions across 14 posts, in 15 distinct kinds. The most used accounts for 27.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😭 | 36 | 27.5% | |
| 👍 | 18 | 13.7% | |
| ⚡ | 14 | 10.7% | |
| 👏 | 8 | 6.11% | |
| 💔 | 8 | 6.11% | |
| 🤩 | 8 | 6.11% | |
| ❤ | 7 | 5.34% | |
| 🤔 | 7 | 5.34% | |
| 😍 | 6 | 4.58% | |
| 🤣 | 5 | 3.82% | |
| 👌 | 4 | 3.05% | |
| 😁 | 4 | 3.05% | |
| 💯 | 3 | 2.29% | |
| 🏆 | 2 | 1.53% | |
| 🐳 | 1 | 0.763% |
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 14 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 131 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 2 November 2023 to 31 December 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
新年快乐! 恭喜五位幸运跨年人
😍6
Posted without readable text
👍1
虽然我们业务恢复进度受到阻碍,暂时可能无法立刻恢复 但我们依旧为各位准备了奖品给各位庆祝今年圣诞节 要求 - 除了加入本频道外,还需要加入一个临时频道 以保证活动公平性 在这里,我仅代表所有Kamiya管理员祝各位圣诞节以及新年快乐 — Sam
👍10❤2
Posted without readable text
Posted without readable text
❤1
一段声音的自白。【REECHO AI语音技术展示】】 https://www.bilibili.com/video/BV18M411o771/?share_source=copy_web&vd_source=32a5c1bfbb528a7129415d68c8be74f1 一个小小的AI声音剧场,大家可以来康康捏
❤3
2023/11/25 REECHO.AI 功能更新 ————————— - 新增模板功能,可以将编辑器中内容保存为模板,并在后续快速套入角色进行生成 - 角色支持设置/修改头像 - 各类细节优化与修复 进度前瞻:我们目前正在为即将到来的重大更新积极开发中,更多细节将在稍后公布
👍2
经OpenAI纪委、监察委调查,Sam Altman严重违反组织纪律和组织规矩,对董事会不忠诚、不老实,处心积虑对抗审查,隐瞒个人心理动向,身为OpenAI的高级领导干部,本应认真贯彻执行公司的路线方针政策,但他理想信念丧失,严重违背八项规定精神,且首届开发者大会后后仍不收敛、不收手,性质恶劣、情节严重。依据《OpenAI纪律处分条例》等有关规定,经董事会批准,决定给予Sam Altman开除AGI籍处分、剥夺ChatGPT之父等一切职务。
🤔7🤣5💯3
2023.11.12功能更新 ———————————————— Reecho开发者API现已初步上线,有开发相关需求及API调用需求可以通过API接口将Reecho提供的语音能力应用到各种项目中了~ 详情可参见开发者文档:https://dev.reecho.ai
都是黑幕
谢谢你们,其实全是黑幕(
😭15
Posted without readable text
🤩8
Showing the 12 most recent of 20 posts we hold for @kamiyanoc. 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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“Kamiya NOC” (@kamiyanoc), 582 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/kamiyanoc.
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.