Telegram RegisterThe public register of Telegram
Telegram profile photo for NiiHost-Channel01

Channel

NiiHost-Channel01

@niihostchannel01

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,020subscribers

+27 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002307497021
TypeChannel
Username@niihostchannel01
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live1 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/niihostchannel01

Growth

9931,0221,007.57 August 2026 — 993 subscribers8 August 2026 — 993 subscribers8 August 2026 — 994 subscribers14 August 2026 — 1,003 subscribers18 August 2026 — 1,007 subscribers20 August 2026 — 1,010 subscribers24 August 2026 — 1,014 subscribers27 August 2026 — 1,017 subscribers30 August 2026 — 1,022 subscribers1 September 2026 — 1,020 subscribers1,0207 August 20261 September 2026
10 measurements spanning 25 days, net +27. 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 989–1,026 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 23:251,020-2
30 Aug 2026, 05:561,022+5
27 Aug 2026, 07:091,017+3
24 Aug 2026, 12:271,014+4
20 Aug 2026, 13:531,010+3
18 Aug 2026, 00:181,007+4
14 Aug 2026, 13:381,003+9
8 Aug 2026, 02:05994+1
8 Aug 2026, 00:34993no change
7 Aug 2026, 14:29993first reading

Engagement

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

Reaction mix

58 reactions across 13 posts, in 13 distinct kinds. The most used accounts for 19.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1119.0%
👎1017.2%
👏915.5%
😁58.62%
🤡58.62%
💩46.90%
😇46.90%
🌚35.17%
23.45%
🤯23.45%
🔥11.72%
🖕11.72%
🤪11.72%

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 19 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 58 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 9 February 2026 to 27 July 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.

Recent posts

27 Jul 2026, 18:23 UTC523 views1 reactionsread 8 August 2026

NiiHost香港服务器托管|机柜资源开放 📍 香港荃湾 iTech Tower 1 Data Center 香港机柜资源,目前开放服务器托管合作客户。 我们采用灵活托管模式: 根据服务器实际功耗 + 网络需求进行配置,不绑定固定套餐。 ━━━━━━━━━━━━━━ 🌐 网络资源 ━━━━━━━━━━━━━━ 提供两种网络接入方案: ① 香港方向保障网络 - 优化香港本地访问及低延迟业务 - 可提供对接 HKGIX 物理跳线 价格: USD 0.20/Mbps/月 ② 香港本地 + 国际网络 - 香港本地网络保障 - 直达 Equinix HK1 / HK2 - 支持全球访问及跨境业务需求 价格: USD 0.35/Mbps/月 ━━━━━━━━━━━━━━ ⚡ 服务器托管 (现在5折优惠) ━━━━━━━━━━━━━━ 首批客户开放优惠价格: USD 0.3/W/月 起 (按照服务器实际功耗计

1

23 Jul 2026, 01:33 UTC661 views0 reactionsread 8 August 2026

NiiHost香港服务器托管|机柜资源开放 📍 香港荃湾 iTech Tower 1 Data Center 香港机柜资源,目前开放服务器托管合作客户。 我们采用灵活托管模式: 根据服务器实际功耗 + 网络需求进行配置,不绑定固定套餐。 ━━━━━━━━━━━━━━ 🌐 网络资源 ━━━━━━━━━━━━━━ 提供两种网络接入方案: ① 香港方向保障网络 - 优化香港本地访问及低延迟业务 - 可提供对接 HKGIX 物理跳线 价格: USD 0.20/Mbps/月 ② 香港本地 + 国际网络 - 香港本地网络保障 - 直达 Equinix HK1 / HK2 - 支持全球访问及跨境业务需求 价格: USD 0.35/Mbps/月 ━━━━━━━━━━━━━━ ⚡ 服务器托管 (现在5折优惠) ━━━━━━━━━━━━━━ 首批客户开放优惠价格: USD 0.3/W/月 起 (按照服务器实际功耗计

21 Jul 2026, 04:42 UTC254 viewsread 8 August 2026
Forwarded from @FF1shChannel

🚀 FF1 v2 正式版-正式经发布 多节点端口转发群控面板 · 跑满物理带宽,不做瓶颈 一个控制台,管好所有中转机。转发、隧道、限速、装机、计量,全在一处编排,改动实时下发到链路上每个节点——告别逐台 SSH 改配置。 【♥️ 加入Nginx 四层转发引擎,抗识别,抗识别!!!!】 旧版本需要升级安装!请注意! 购买地址: https://my.niihost.com/index.php/store/support 7折:FF1 Pro 30% OFF 官方网站或安装方式请登录官网 https://ff1.sh

6 Jul 2026, 05:14 UTC349 views5 reactionsread 8 August 2026
Forwarded from @FF1shChannel

🚀 FF1 v2 正式版即将发布 多节点端口转发群控面板 · 跑满物理带宽,不做瓶颈 一个控制台,管好所有中转机。转发、隧道、限速、装机、计量,全在一处编排,改动实时下发到链路上每个节点——告别逐台 SSH 改配置。 【♥️ 加入Nginx 四层转发引擎,抗识别,抗识别!!!!】 【♥️ 加入Nginx 四层转发引擎,抗识别,抗识别!!!!】 【♥️ 加入Nginx 四层转发引擎,抗识别,抗识别!!!!】 重要事情说三次!!! ━━━━━━━━━━━━━━ ⚡️ 性能就是底线 1Gbps / 10Gbps 网络下,FF1 不是瓶颈。上限只取决于你的硬件与系统网络栈——FF1Core 多引擎智能调度,轻松跑满物理带宽。 🧩 转发规则,像 RouterOS 一样顺手 入口端口 → 目标地址,一条搞定。端口范围/列表同位同号透传,50-60,80,90-200 混合列表一次配好,入口出口一一对应。 🪆 多层转发(套娃)

👏3👍2

6 Jul 2026, 05:14 UTC≈1,090 views3 reactionsread 8 August 2026

NIIHOST 购买5折优惠!

🌚1🔥1🤪1

18 Jun 2026, 15:21 UTC≈1,460 viewsread 8 August 2026

通知 Nezha 哪吒探针出发现大安全漏洞。 请有安装哪吒探针的客户尽快自查,避免导致停机,给您带来损失。

15 Jun 2026, 13:25 UTC≈1,430 views6 reactionsread 8 August 2026

TW线路维护通知 2026/06/16(星期二)05:00~08:00将对TW现有的线路进行维护。 持续时间大概为20分钟,期间IP会有可能暂时不可用。 NiiHost Team

🤡3🌚2👎1

4 Apr 2026, 17:25 UTC≈1,930 viewsread 8 August 2026

各位IEPL用户 由于目前资源有限,IEPL恢复还需要一些时间,为了用户的利益,我们推出2个解决方案: 方案一:如果用户同意,可以为用户切换到TW的线路,按照3月18日起折算余额,将余额用于TW的主机,另外再额外补偿1周时间。 方案二:如果用户能够等待,我们近期会有新的线路资源部署,待到新的资源部署到位,为用户办理迁移。 以上两个方案,如果用户希望执行方案一,请发工单(说明期望迁移到的目标TW套餐),我们会有客服跟进。

1 Apr 2026, 03:19 UTC≈1,510 views1 reactionsread 8 August 2026
Photo

NiiHost 香港高速建站机 现已优惠上线 特性:低延迟,高速网络,高端3C精,与IEPL相当,线路漂亮 CN2+CMI+CUG三网精品网络, 适用于:免备案建站,跨境网络高速传输,CDN加速,直播加速 购买链接:https://my.niihost.com/index.php/store/hongkong-3c-bgp 现有 IEPL客户如果意向,我们骨折优惠。

👍1

28 Mar 2026, 16:24 UTC≈1,160 viewsread 8 August 2026
Photo

通了,正在上线了,颜值高不高? IEPL GEN3 第三代 NAT N5 恢复 独立IP 恢复

25 Mar 2026, 11:35 UTC≈1,020 views2 reactionsread 8 August 2026

通知: IEPL - N5 已全部开好, 您的机器将全变成 IEPL GEN3 xxxxx 三代IEPL , 由于我们展示系统还没有跟上,如果有端口范围请与我们联系。我们也会一对一发消息。 另有二个客户找到不信息。请有N5没开机的请与我们联系。我们立刻帮您开机。

😁2

25 Mar 2026, 04:56 UTC939 views3 reactionsread 8 August 2026

通知: IEPL 独立IP / N5 用户请通过香港IP地址和端口 SSH SFTP 备份您的数据。 我们即将开放新服务器。GEN3 第三代目IEPL 请尽快。备份。如无需备份我们将直接回收新开。 NAT 用户我们将在本周内恢复,NAT我们只会服务于已购买用户了,暂不打算接受新用户。

1👍1😁1

Showing the 12 most recent of 19 posts we hold for @niihostchannel01. 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.

Forward network

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.

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

“NiiHost-Channel01” (@niihostchannel01), 1,020 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/niihostchannel01.

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.