Telegram RegisterThe public register of Telegram
Telegram profile photo for 魔戒-按量计费机场

Channel

魔戒-按量计费机场

@The_Lord_Rings

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

77,072subscribers

+11,187 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001257965944
TypeChannel
Username@The_Lord_Rings
Description加入我们,随我们探索中土世界! 最新消息、优惠推送,建议关注 地址: 魔戒.com
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/The_Lord_Rings

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 65% 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 the other topics.

Growth

65,88577,07271,478.56 August 202615 November 2026
65 measurements spanning 101 days, net +11,187. 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 64,207–78,750 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
15 Nov 2026, 03:4677,072+275
11 Nov 2026, 21:3976,797+157
9 Nov 2026, 23:0576,640+61
8 Nov 2026, 13:0776,579+98
7 Nov 2026, 04:0676,481+96
6 Nov 2026, 00:5476,385+64
5 Nov 2026, 02:5676,321+89
4 Nov 2026, 01:5976,232+49
3 Nov 2026, 04:2876,183+88
2 Nov 2026, 02:3676,095+91
31 Oct 2026, 23:1576,004+72
31 Oct 2026, 02:1875,932+93
30 Oct 2026, 05:0875,839+118
29 Oct 2026, 01:3175,721+161
27 Oct 2026, 22:1675,560+143
26 Oct 2026, 20:2775,417+101
25 Oct 2026, 22:4675,316+95
25 Oct 2026, 01:3675,221+52
24 Oct 2026, 03:5975,169+99
23 Oct 2026, 04:0875,070first reading

Engagement

31 posts held, back to 7 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 207 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
47.1%
avg views ÷ 77,072 subscribers
Avg views / post
36,300
8 posts measured
Reaction rate
0.098%
reactions ÷ views · ER floor
Posts in window
8
of 31 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 7 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held31 (7 February 2025 – 11 November 2026)
Views total290,200
Reactions total229
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 08:39 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
54
Links
42

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

235 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8435.7%
👍6628.1%
😱6628.1%
🤡135.53%
👎41.70%
🍌20.851%

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

Measured over the 31 most recent posts we hold, published 7 February 2025 to 11 November 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

Telegram’s own ‘edited’ marker: 4 of 8 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 16:04 UTC≈15,200 views84 reactionsread 17 November 2026

Posted without readable text

👍43❤27😱12🍌2

7 Nov 2026, 15:46 UTC≈25,400 views19 reactionsread 17 November 2026

我们调整了一些策略以改善体验和提升到账速度 以下场景无需再等待48小时: 如果提现地址与上次地址一致,则无需等待48小时 发起提现后,回复邮件确认,则无需等待48小时 当系统认为提现可能不是您本人发起,则需要邮件确认: 地址变更和首次提现,需要邮件进行二次确认,确认后进入提现流程 我们致力于完善安全措施,以保护您的账户和资金安全。

❤13👍6

1 Nov 2026, 09:47 UTC≈29,200 views31 reactionsread 17 November 2026

AFF 佣金提现安全升级 为保障大家的佣金安全,我们对佣金提现流程做了以下升级,补上此前流程中的安全短板: 提现申请邮件通知 每次提交佣金提现,系统都会立即向账号注册邮箱发送通知,内容包括提现方式、打码后的收款账号和工单号。 提现统一延后 48 小时处理 提现申请提交满 48 小时后才会进入处理,给您留出核实和拦截的时间。 关闭工单即可拦截 如果收到提现通知,但不是您本人操作: · 立即修改密码,修改后所有已登录设备会被强制下线 · 重新登录,在「我的工单」中关闭该提现工单 · 联系在线客服协助核查账号 工单关闭后,这笔提现不会被处理,佣金余额不受影响。48 小时内越早操作,拦截成功率越高。 收款地址变更人工复核 收款地址与上次提现不一致时,工作人员会重点核对后再处理。 请使用与其他网站不同的密码,并留意注册邮箱的通知。部分邮箱可能会把通知归入垃圾邮件。

👍17❤10👎4

1 Nov 2026, 09:20 UTC≈25,400 views71 reactionsread 17 November 2026

我们已于昨日更新一个严重的账户安全漏洞 漏洞会把俩个字符串相同(数据库认为的相同)当作同一个邮箱,然而数据库认为相同不等于这俩邮箱就是相同的 例如被攻击用户的邮箱是 [email protected] ,攻击者只需要控制 admin@éxample.com 然后在找回密码页面输入 admin@éxample.com ,会匹配到邮箱[email protected]对应的账号,但是实际上邮件验证码是被发送到admin@éxample.com的,然后攻击者就成功获取了重置密码所需的验证码并修改了 [email protected] 的密码 我们已向可能被泄漏的客户发送了邮件。 但是我们仍建议您检查并进行密码轮换。

😱54🤡13❤4

31 Oct 2026, 10:47 UTC≈26,600 views23 reactionsread 17 November 2026

关于账号密码的安全提醒 尊敬的用户: 近期我们监测到,有人用邮箱和密码,批量尝试登录魔戒账号,也就是俗称的"撞库"。 从攻击特征看,这通常是因为同一个密码在其他网站也用过并且泄露了,或者密码过于简单,而不是魔戒的数据库。但如果您在魔戒和其他网站用的是同一个密码,攻击者就能用它直接登录您的魔戒账号。目前已有一部分账号被这样登录过。 攻击者对每个账号只试一次,"密码错误次数过多自动锁定"的保护对这种方式不起作用。我们已经采取措施拦截这类登录,并会逐一发邮件通知受影响的用户。 为保护您的账号和剩余流量,请您: 1. 修改密码:登录后在「个人中心」修改密码,新密码不要和其他网站相同。如果您在多个网站使用同一个密码,我们强烈建议您立即修改。 2. 重置订阅:在「个人中心」点击「重置订阅信息」,再到客户端里重新导入新的订阅链接。旧链接会立即失效,他人无法再使用您的流量。 3. 停止使用统一密码: 近期安全事件频发,尤其在10月曝…

❤23

20 Oct 2026, 13:40 UTC≈57,500 viewsread 17 November 2026

已经恢复,我们仍在持续观察。 更新公告时间会稍迟,我们仍在投入工作。缓解中断和完善方案。 建议您更新订阅后使用

20 Oct 2026, 12:24 UTC≈55,500 views1 reactionsread 17 November 2026

更新订阅后有所缓解,但是我们尚未彻底修复。我们仍在进行中 非常抱歉对您的体验造成了影响,我们正在积极处理

❤1

20 Oct 2026, 06:34 UTC≈55,400 views0 reactionsread 17 November 2026

【部分恢复】节点故障处理进展 VMess 节点:已恢复 AnyTLS 节点:不可用,正在处理中 HY2(Hysteria2)部分地区不可用 请更新订阅,更新失败请前往官网重新导入 持续观察中,非常抱歉对您的使用造成了影响。

7 Sept 2026, 10:19 UTC≈117,000 views1 reactionsread 17 November 2026

【已恢复】当前系统存在部分故障: 魔戒网站 已恢复 客户端 已恢复 在线客服 已恢复 节点超时 已恢复 我们已修复全部故障,非常抱歉对您的使用造成了影响。

❤1

10 Aug 2026, 16:55 UTC≈153,000 viewsread 17 November 2026
Photo

网站升级已完成 现在您的订阅不会被新订阅覆盖,多个订阅会并列显示。 以解决续费必损失流量,或必须完全用完再续费的二选一难题

10 Aug 2026, 13:53 UTC≈127,000 viewsread 17 November 2026
Photo

【网站系统升级维护】 我们稍后将对网站进行一次升级,此次升级会造成短暂的网站无法访问。 您的节点和连接不会受影响,仍可继续使用,不会中断。 影响访问仅限网站访问、网站登录、更新订阅。

22 May 2026, 14:38 UTC≈137,000 views3 reactionsread 17 November 2026

【安全更新通知】请尽快修改账号密码 我们近期接到 V2Board / Xboard 系列面板的安全更新通报 "找回密码" 接口存在一处验证缺陷,理论上攻击者在提前知晓用户邮箱的情况下,可能触发异常密码重置。 目前魔戒安全补丁已部署完成,漏洞已封堵。 如果您的邮箱不曾暴露,这次漏洞对您的影响有限。此次影响主要是AFF推广用户。如果您同时在多个站点拥有相同邮箱的账户,为了您的账号安全,我们建议您(定期修改密码是个很好的习惯,如果您方便,建议您安排时间也进行修改密码): 1. 立即修改账号密码,使用此前未使用过的强密码。并重置订阅 2. 检查近 7 天的订单、订阅、提现记录 是否存在异常 3. AFF 推广用户 请额外检查佣金余额和近期工单 4. 如发现任何异常,请第一时间通过工单联系客服 期间AFF推广用户如果被盗用提现请尽快联系我们,我们会核实,如果损失属实,损失由我们承担。 我们已升级了密码重置接口的校验逻辑,并…

❤3

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

Mentions

Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

离港一二线机场收录&测评|配置🅥
@airport_cn · 16,700
#1
冲浪小贴士
@Gfwpro · 21,047
#2
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,633
#3
TKV Network
@tkv_ktv · 2,418
#4
机场稽查局
@VPN_Police · 8,338
#5
甜甜圈
@tian52200 · 2,557
#6
海豚机场测评|用户侧体验|测速频道
@haitun_channel · 39,301
#7
FreeKing
@FreeKingX · 406
#8
飞鸟云
@fnyun · 1,606
#9
Mujika Network | Channel
@mujika_channel · 1,744
#10
翻翻墙 | 机场评测
@ffqchannel · 69,720
#11
無名の更新频道
@iwuming_channel · 4,739
#12
雪橇雲公告 SledCloud News
@SledCloudNews · 2,478
#13
免费高速订阅节点
@freeVPNjd · 24,161
#14
八戒-提供优质的网络服务
@bajievs · 6,102
#15
Yummy 😋
@GodlyNews1 · 71,283
#16
晚来天欲雪 🅥 🌈🌝🐳🏳️‍🌈 limbopro.com 🔗
@limboprossr · 17,931
#17
在花🎗️科技圈
@zaihuapd · 290,897
#18
白嫖机场节点VPN免费分享频道
@WFVPN · 41,046
#19
24小时出租车服务📲🚕
@TAXI333666999 · 157
#20
金十数据 闪电资讯
@jin10news · 5,459
#21
XAutoDaily
@XAutoDaily · 16,862
#22

Read from Telegram’s recommendation API, most recently 28 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

冲浪小贴士
@Gfwpro · 21,047
Telegram ranks this channel #2 of 33 here — alongside 32 others — read 28 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“魔戒-按量计费机场” (@The_Lord_Rings), 77,072 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/The_Lord_Rings.

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.