Telegram RegisterThe public register of Telegram
Telegram profile photo for Hats Network Inc.

Channel

Hats Network Inc.

@hatsnet

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

42subscribers

-5 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-1001655505941
TypeChannel
Username@hatsnet
CreatedBetween 1 December 2021 and 5 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live6 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/hatsnet

Topic

Other / unclassifiable — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

424744.57 August 2026 — 47 subscribers10 August 2026 — 47 subscribers25 September 2026 — 43 subscribers6 October 2026 — 42 subscribers7 August 20266 October 2026
4 measurements spanning 59 days, net -5. 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 41–48 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 00:5942-1
25 Sept 2026, 07:1743-4
10 Aug 2026, 13:4647no change
7 Aug 2026, 21:1947first reading

Engagement

20 posts held, back to 5 February 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 16 September 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

36 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 47.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1747.2%
🎉1233.3%
🥰719.4%

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 9 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 36 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 5 February 2023 to 16 September 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

16 Sept 2024, 16:03 UTC169 views4 reactionsread 10 August 2026
Photo

帽子網絡(香港)恭祝全球華人2024年中秋快樂!願您闔家團圓,共享明月清輝。 🎉🏮🥮🏮🎉 Happy Mid-Autumn Festival 2024! May you bask in the glow of the full moon and cherish precious moments with your loved ones. Hats Network Inc, (Hong Kong).

🥰4

9 Feb 2024, 15:57 UTC229 views5 reactionsread 10 August 2026
Photo

帽子網絡(香港)恭祝全球華人: 龍年快樂,吉祥如意,萬事順心! 2024 · 農曆甲辰年 ©Hats Network Inc AS203314

❤5

3 Jan 2024, 03:00 UTC206 viewsread 10 August 2026

To Customer / Peering: We regret to inform you that AS203314 Netherlands - Amsterdam (AMS - NL-IX) is nearing its expiration and will not be renewed. This decision aligns with our strategic focus on the Asia-Pacific backbone in 2024, aiming to optimize costs by eliminating non-essential idle expenditures. We understand the inconvenience this may cause, but this step is essential for the efficiency and sustainabilit…

29 Sept 2023, 07:17 UTC298 views7 reactionsread 10 August 2026
Photo

✨ 帽子網路(香港)恭祝全球各地华人 2023 年中秋節快樂,願您與家人團圓! 🎉 🎉 🎉 Happy Mid-Autumn Festival! May you enjoy this special time with your loved ones and celebrate the beauty of the full moon together. Hats Network Inc, (Hong Kong).

🎉4❤3

8 Sept 2023, 04:11 UTC368 views0 reactionsread 10 August 2026

✅ HKG3 上游的大规模攻击已由 CFMT 缓解,所有路由已恢复。 Massive Attack Upstream Mitigated by Cloudflare Magic Transit.

31 Aug 2023, 14:59 UTC389 viewsread 10 August 2026

❌由于 HKG3 上游遭到大规模攻击, HKG3 到 HE (AS6939) Session 暂时离线。 Due to a massive attack on upstream, HKG3 to HE (AS6939) BGP Session is temporarily down.

23 Aug 2023, 11:01 UTC950 viewsread 10 August 2026

亚太核心节点升级完毕,在 HKG 及 SIN 核心路由器间使用 iperf3 10Gbps 固定满载速率 TCP 单线程及多线程多次测试结果: BBR v3 单线程包重传数量相比 BBR v1 减少 8-15% 左右,满载延迟抖动明显降低。 另外在较高抖动和丢包率的场景下 BBR v3 的抖动率相对 BBR v1 更低,丢包率缓解效果相差不大。 传输相同文件, BBR v3 所用流量比 BBR v1 更少。 https://github.com/google/bbr/tree/v3

23 Aug 2023, 07:25 UTC375 viewsread 10 August 2026

Dear Valued Customer, We are currently performing routine maintenance on our network infrastructure in the Asia Pacific region. The primary objective of this maintenance is to upgrade the system kernel of core network nodes in the region to Linux 6.4.0+ and to upgrade the BBRv1 congestion control module to BBRv3. Upon completion of the maintenance, the overall TCP throughput performance of the Hats network will be…

10 Aug 2023, 00:31 UTC302 viewsread 10 August 2026

🇸🇬 SIN1 Network connectivity progress: ▎AS2914 NTT✅Connected ▎AS174 Cogent ✅Connected ▎AS6939 Hurricane Electric ✅Connected ▎Equinix IX - Singapore ✅Connected (From our Upstream)

31 Jul 2023, 13:46 UTC302 viewsread 10 August 2026
Photo

🇸🇬 Hello! Singapore. ▎We are thrilled to announce the launch of Hats Network (AS203314)'s latest Core Point of Presence (PoP) facility in Singapore (SIN1). ▎This significant milestone marks the opening of our third core network node in Asia, complementing our existing facilities in Hong Kong and Taipei. ▎Our primary objective is to establish a robust, sustainable, and high-quality network infrastructure in Singapo…

Showing the 12 most recent of 20 posts we hold for @hatsnet. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.

“Hats Network Inc.” (@hatsnet), 42 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/hatsnet.

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.