Telegram RegisterThe public register of Telegram

Channel

Lime Network Channel

@LimeNetwork_Channel

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

586subscribers

+17 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002836026162
TypeChannel
Username@LimeNetwork_Channel
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/LimeNetwork_Channel

Growth

569586577.56 August 2026 — 569 subscribers6 August 2026 — 573 subscribers6 August 2026 — 573 subscribers12 August 2026 — 586 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net +17. 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 566–589 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 13:13586+13
6 Aug 2026, 18:03573no change
6 Aug 2026, 10:50573+4
6 Aug 2026, 05:17569first reading

Engagement

20 posts held, back to 10 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
163.0%
avg views ÷ 586 subscribers
Avg views / post
955
9 posts measured
Reaction rate
0.582%
reactions ÷ views · ER floor
Posts in window
9
of 20 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 9 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 6 August 2026
Posts held20 (10 November 20256 August 2026)
Views total8,598
Reactions total44
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:03 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.

Reaction mix

74 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 37.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡2837.8%
💩1723.0%
😁1013.5%
912.2%
🤣45.41%
🤓22.70%
👎11.35%
🗿11.35%
🤮11.35%
🤯11.35%

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 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 74reactions 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 10 November 2025 to 6 August 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

6 Aug 2026, 12:45 UTC175 viewsread 6 August 2026

莱姆下一步可能往屋子马路的方向靠近?(不一定)

6 Aug 2026, 12:39 UTC198 views5 reactionsread 6 August 2026

莱姆可能会变质,但是不会倒闭

🤣4🤡1

6 Aug 2026, 03:42 UTC444 views6 reactionsread 6 August 2026

群会留着,以后如果能重开就重开,实在不行留着聊聊天也挺好的,老板心里现在很悲伤

🤡6

6 Aug 2026, 03:30 UTC528 views7 reactionsread 6 August 2026

或者谁能帮我搞到几个大客户可能就不暂停了,现在成本太高已经亏麻了

🤡7

6 Aug 2026, 03:27 UTC549 views6 reactionsread 6 August 2026

后期可能会重开,但是现在真的要停一停了,亏得受不了了

🤡6

6 Aug 2026, 03:26 UTC≈2,120 views16 reactionsread 6 August 2026

【重要公告】LIME NETWORK 暂停营业及数据迁移通知 尊贵的 LIME NETWORK 用户: 感谢大家一直以来对 LIME NETWORK 的支持与信任。 非常遗憾地通知大家,由于上游服务账单成本超出承受范围,加之老板一个人精力有限、无力继续进行品牌运营与日常维护,经过慎重考虑,我们决定正式暂停 LIME NETWORK 的业务运营。 具体安排及注意事项如下: 1. 暂停营业时间 本站将于 2026 年 8 月 7 日(周五)00:00 正式停止服务并关闭节点与系统。 2. 用户数据备份与迁移提醒(重中之重) 请所有用户务必于 2026 年 8 月 7 日前 完成个人数据、配置文件及相关资产的本地备份与迁移。 关停时间节点过后,服务器及数据库将进行清空处理,届时所有数据将无法找回,请大家务必提前做好准备,以免造成不必要的损失。 对于此次暂停营业给您带来的不便,我们致以最诚挚的歉意。再次感谢大家一路以来的陪伴与理解

😁8🤡7🤯1

21 Jul 2026, 09:42 UTC859 viewsread 6 August 2026

由于老板想有诚意一点,给大家直接放福利了,不需要解锁阶段了 全场(不含闪购)75折优惠码 hQ5cJ2fL 剩下的IP不多了,卖完即止 销售额达到500USD的大奖继续保留

17 Jul 2026, 11:44 UTC795 views2 reactionsread 6 August 2026

P.S. 解锁新的阶段后,前面解锁的用户将选择神秘大礼(返现/配置升级/加赠时间/特殊优惠码等)

1🤡1

17 Jul 2026, 10:08 UTC≈2,930 views2 reactionsread 6 August 2026

🎉 Limee.host 周年庆 🎉 ━━━━━━━━━━━━━━━━━━━━━━━━ 🔥 三重优惠,逐级解锁 🔥 阶段一【进行中】→ 85折 阶段二【$200解锁】→ 8折 阶段三【$300解锁】→ 75折 💰 阶段越高,折扣越狠! ━━━━━━━━━━━━━━━━━━━━━━━━ 🇭🇰 香港BGP | 国际优化线路 🇯🇵 日本BGP | JPIX+PCCW多线路 🏠 日本家宽 | SoftBank原生IP ⚡️ 手慢无!IP池见底了! ━━━━━━━━━━━━━━━━━━━━━━━━ 🏆 $500 全员普惠大奖 🏆 当活动收入达到 $500 🎁 全员福利 每位参与者获 $2 账户余额 直接用于续费,无门槛 🥇 消费TOP3 第1名:免费续费1个月 第2名:$10 余额券 第3名:$5 余额券 🎰 锦鲤抽奖 从所有参与者中抽1人 送 HK-BGP-Premiu

1🗿1

7 Jul 2026, 03:10 UTC674 viewsread 6 August 2026

HK BGP产品IP迁移已经完成 旧IP 82.25.47.X 新IP 200.180.165.X 新IP尾数不变,经过测试已经全球可访问

6 May 2026, 09:32 UTC934 viewsread 6 August 2026

P.S. HK-Connect产品为中国大陆移动优化产品,南方移动直连,可拉流

6 May 2026, 09:16 UTC933 views3 reactionsread 6 August 2026

Lime Network|2026劳动节开工特惠 在开工第一天,我们为大家带来了所有区域全部产品的开工特惠! For 个人用户,我们带来了香港和日本区域的全线特惠 🇭🇰香港全线产品(包括HKBGP和HKCONNECT) 年付75折 WORKERSDAY25OFF 月付9折 WORKERSDAY10OFF 🇯🇵日本区域全线产品(包括JPBGP和JPHOME) 年付7折WORKERSDAY30OFF (仅包含JPBGP产品) 月付8折 WORKERSDAY20OFF (包含日本区域所有产品) 🚀 机场主专属 BGP 特惠 定制大流量机器仅需1USD/TB起 详情请咨询在线客服 @Lime_AS251023 📅 活动期间限时供应,售完即止 🛒 官网下单: limee.host 💬 联系客服: @Lime_AS215023

🤓2👎1

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

Citation-graph rank

Citation-graph rank — 286,079 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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

“Lime Network Channel” (@LimeNetwork_Channel), 586 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/LimeNetwork_Channel.

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.