Telegram RegisterThe public register of Telegram
Telegram profile photo for noc@sunoaki.net

Channel

[email protected]

@sunoaki

On this record: Topic · Growth · Engagement · Posts · Cite this entry

11subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002438336583
TypeChannel
Username@sunoaki
Created18 February 2025 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live7 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/sunoaki

Topic

Technology — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 52% 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

911107 August 2026 — 9 subscribers12 August 2026 — 9 subscribers31 August 2026 — 10 subscribers7 October 2026 — 11 subscribers7 August 20267 October 2026
4 measurements spanning 60 days, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 03:1811+1
31 Aug 2026, 14:3410+1
12 Aug 2026, 13:029no change
7 Aug 2026, 23:429first reading

Engagement

4 posts held, back to 18 February 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 4 posts for this entry, the most recent from 1 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Mar 2026, 15:59 UTC75 viewsread 12 August 2026

尊敬的客户: 您是否曾因物理链路故障导致 BGP Session 陷入永恒的 Idle?您是否在茂密的 XC 线缆丛林中迷失,至今未找到通往交换机的正确路径?您是否经历过因路由表过载导致风扇狂转,其产生的气流不幸吹飞了您苦心经营的配线架标签? Sunoaki Network LLC 懂您的焦虑。 即日起,我们正式启动 IP over Avian Carriers (IPoAC) DIA/IPT 交付计划。摒弃脆弱的光纤与昂贵的铜缆,拥抱大自然最纯粹的生物电路,彻底解决您的物理层烦恼。 服务内容 提供基于 IPoAC 协议的 Direct Internet Access / IP Transit 服务。 视具体需求,提供的带宽取决于鸽子飞行速度、风向和是否中途停下来吃面包屑,不设服务上限(上限取决于鸽巢容量)。Sunoaki 将在收到请求的若干个工作日派出我们的工作人员至客户选择的交付地点进行配置。(基础时间为五个工作…

Signed 924584

Showing the 4 most recent of 4 posts we hold for @sunoaki. 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.

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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“[email protected]” (@sunoaki), 11 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/sunoaki.

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.