Telegram RegisterThe public register of Telegram
Telegram profile photo for 荷鲁斯机场【官方频道】🔥

Channel

荷鲁斯机场【官方频道】🔥

@ihorus9

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

165subscribers

-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-1001906252025
TypeChannel
Username@ihorus9
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/ihorus9

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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

165168166.57 August 2026 — 167 subscribers8 August 2026 — 167 subscribers15 August 2026 — 168 subscribers6 September 2026 — 167 subscribers26 September 2026 — 166 subscribers7 October 2026 — 165 subscribers7 August 20267 October 2026
6 measurements spanning 61 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 165–168 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 10:15165-1
26 Sept 2026, 12:38166-1
6 Sept 2026, 07:36167-1
15 Aug 2026, 03:35168+1
8 Aug 2026, 15:46167no change
7 Aug 2026, 10:31167first reading

Engagement

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

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 1 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 1 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 16 April 2024 to 29 September 2025, 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

29 Sept 2025, 03:53 UTC409 viewsread 8 August 2026

月底至月初会有不间断升级,维护好后,免费7天使用

Signed 荷魯斯官方客服

17 Sept 2024, 01:30 UTC594 viewsread 8 August 2026

本站于 10 月 1 日起,需要邀请 码才可以注册 实行半封闭状态

Signed 荷魯斯官方客服

4 Sept 2024, 11:56 UTC607 viewsread 8 August 2026

今天己更新国内订阅地址,请重庆北京地区更新订阅地址。有问题私聊我,@Adolfcn

Signed 荷魯斯官方客服

6 Aug 2024, 06:59 UTC650 viewsread 8 August 2026

为防止域名污染,请大家手动修改一下手机和电脑端的dns ,修改成 114.114.114.114 223.5.5.5 8.8.8.8

Signed 荷魯斯官方客服

6 Aug 2024, 06:57 UTC607 viewsread 8 August 2026

新域名己经上线,请河南地区,新疆,福建地区测试一下,还有最近河北地区

Signed 荷魯斯官方客服

21 Jul 2024, 04:45 UTC540 viewsread 8 August 2026

免流了10天,以应对域名变更产生的问题,域名重新更新,河南,福建地区测试

Signed 荷魯斯官方客服

5 Jul 2024, 17:25 UTC495 viewsread 8 August 2026

己经恢复,7.7周日,免流量一天,后续增加节点

Signed 荷魯斯官方客服

24 Jun 2024, 12:23 UTC495 viewsread 8 August 2026
Poll

你理想的的套餐标准?

  1. 无倍率 月流量90G32%
  2. 无倍率 月流量100G29%
  3. 无倍率 月流量200G6%
  4. 无倍率 不限流量300G32%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Signed 荷魯斯官方客服

24 Jun 2024, 12:17 UTC403 viewsread 8 August 2026

应老客户要求,7月将会重新上架不限时套餐,敬请期待

Signed 荷魯斯官方客服

24 Jun 2024, 08:34 UTC375 viewsread 8 August 2026

重新更换了订阅域名,app 不受 影响,第三方和 clash 订阅需要重新订阅,新疆,海南,福建理论可以正常使用了。给大家带来不便,深感抱歉

Signed 荷魯斯官方客服

24 Jun 2024, 03:16 UTC336 viewsread 8 August 2026

下午可能会会维护一下,目前临时恢复

Signed 荷魯斯官方客服

23 Jun 2024, 13:48 UTC345 viewsread 8 August 2026

福建江苏新疆地区的铁子私信或在群里发个消息

Signed 荷魯斯官方客服

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

24 Jun 2024, 12:23 UTCAnonymous Poll31 voters

你理想的的套餐标准?

  1. 无倍率 月流量90G32%
  2. 无倍率 月流量100G29%
  3. 无倍率 月流量200G6%
  4. 无倍率 不限流量300G32%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 16 April 2024 to 29 September 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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.

“荷鲁斯机场【官方频道】🔥” (@ihorus9), 165 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/ihorus9.

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.