Telegram RegisterThe public register of Telegram
Telegram profile photo for Mana Edge 专线机场

Channel

Mana Edge 专线机场

@manaedge

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

123subscribers

+1 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-1002432197402
TypeChannel
Username@manaedge
Created5 February 2025 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live3 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/manaedge

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

1221281257 August 2026 — 122 subscribers9 August 2026 — 122 subscribers16 August 2026 — 128 subscribers24 August 2026 — 125 subscribers31 August 2026 — 124 subscribers17 September 2026 — 122 subscribers3 October 2026 — 123 subscribers1237 August 20263 October 2026
7 measurements spanning 57 days, net +1. 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 121–129 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 11:57123+1
17 Sept 2026, 20:20122-2
31 Aug 2026, 09:17124-1
24 Aug 2026, 10:55125-3
16 Aug 2026, 08:26128+6
9 Aug 2026, 03:32122no change
7 Aug 2026, 15:07122first reading

Engagement

6 posts held, back to 5 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 6 posts for this entry, the most recent from 16 February 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤250.0%
👍250.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 3 of the 6 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 5 February 2025 to 16 February 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

16 Feb 2025, 13:59 UTC≈1,140 views2 reactionsread 9 August 2026

ManaEdge IEPL专线机场 所有套餐包含IEPL专线入口 轻量套餐 - 9.9元/60GB 标准套餐 - 19元/150GB 高级套餐 - 39元/300GB 专线入口 1.0 倍率 普通中转 0.5 倍率 频道:@manaedge 群组:@manaedge_group https://manaedge.com 开业七折优惠码:helloworld 订阅频道+加入群组以获取最新优惠信息

❤1👍1

13 Feb 2025, 07:09 UTC691 views1 reactionsread 9 August 2026

ManaEdge 为您提供领先的稳定跨境网络服务,IEPL专线保障您的网络畅通,畅享全球网络无缝连接 无论您是工作精英、游戏达人,还是流媒体内容的狂热粉丝,我们的跨境专线服务都能为您提供极速、稳定的网络体验。凭借独特的技术优势,我们为您打造了一条与众不同的全球网络之路。 ⚡ 高速稳定,全球畅游 通过运营商IEPL/IPLC专项优化跨境线路和国际出口节点,我们的网络连接稳定无忧,确保您随时随地享受如本地般的极速上网体验。无论是高清流媒体观看还是重要的工作会议,网络质量始终如一。 🛡️ 顶级加密,隐私零泄露 采用非对称加密技术,您可以放心在全球范围内畅游互联网,所有数据都将得到安全保护。无设备、IP限制,随时切换设备或网络环境都能保持高速连接。 🚀 极速体验,无卡顿 我们提供的高速带宽,即便在晚高峰时段,也不会限制速度,确保您畅享极致体验。无论是看片、炒币还是远程工作,都能尽享不卡顿、低延迟的流畅体验。

👍1

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

“Mana Edge 专线机场” (@manaedge), 123 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/manaedge.

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.