📣 Ueoly Network | 双十一全球狂欢 双十一狂欢开启,畅连全球,购享不停。感谢大家一直以来对 Ueoly Network 的支持与陪伴。本次双十一特别推出限时优惠,全套餐均可享受专属 8.5 折折扣。 🎁 活动优惠 • 全套餐 | 8.5 折 • 优惠码: DE1111 🗓️ 活动时间 • 2026/11/05 0:00 – 2026/11/11 23:59 (CST) 💡 温馨提示 活动期间下单时输入优惠码 DE1111,即可享受对应优惠。 优惠券仅在活动时间内有效,逾期自动失效,每位用户限用 1 次,全套餐通用。 请确认优惠券输入正确(区分大小写)。如有疑问,请联系发送工单或在线客服协助处理。 Ueoly Network | 让每一次访问,都更加流畅。

Channel
UeolyNetworkCannel
@UeolyNetworkChannel
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
212subscribers
-25 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 | -1003309945401 |
|---|---|
| Type | Channel |
| Usernames | @BeckyNetworkChannel @UeolyNetworkChannel |
| Created | 12 December 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/UeolyNetworkChannel |
Topic
Ecommerce storefront — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 08:06 | 212 | +4 |
| 6 Nov 2026, 17:22 | 208 | +204 |
| 3 Nov 2026, 13:19 | 4 | -205 |
| 13 Sept 2026, 21:37 | 209 | -8 |
| 6 Sept 2026, 12:40 | 217 | +14 |
| 28 Aug 2026, 21:54 | 203 | +7 |
| 21 Aug 2026, 20:15 | 196 | +19 |
| 14 Aug 2026, 16:05 | 177 | -60 |
| 7 Aug 2026, 02:45 | 237 | no change |
| 6 Aug 2026, 21:16 | 237 | first reading |
Engagement
29 posts held, back to 12 December 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 2 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 70.1%
- avg views ÷ 212 subscribers
- Avg views / post
- 149
- 17 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 17
- of 29 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.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 29 (12 December 2025 – 4 November 2026) |
| Views total | 2,528 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 17:22 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
13 reactions across 1 post, in 5 distinct kinds. The most used accounts for 30.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 30.8% | |
| 🔥 | 3 | 23.1% | |
| 😍 | 3 | 23.1% | |
| ❤ | 2 | 15.4% | |
| 🥰 | 1 | 7.69% |
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 2 of the 29 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 12 December 2025 to 4 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: 5 of 17 posts held from the last 30 days (29.4%) 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).
恢复了恢复了
预计20:00宿主机维护
注册已重新开放 稍后将对批量注册的机器账号、无任何信息账号进行清除
注册暂时仅限邀请
📣SLA降级补偿公告 因为不可抗力导致的GFW大规模封锁 近日我站节点部分接入点出现小规模波动。 我们第一时间发现并着手处理,最快速度修复的同时部署了新的容灾方案以应对未来几天的高墙影响。 我们将在稍后为所有有效用户发放30GB 流量使用减免补偿(使用未达30GB则重置流量)并延长3 天有效期。 此次波动属于不可抗力,请您谅解。 已完成发放
维护一下 挂了一点 更新订阅食用
📣 系统维护通知 我们将于 15:30(CST,UTC+8) 进行服务器维护,预计维护时长约 2 小时。 维护期间,网站访问、用户登录、订阅及购买续费等功能将暂时不可用。
9折优惠码 10OFF 有效期至10/30 00:00
服务进行更新 约20min 已恢复 同步更新了一下前端界面 新增了礼品卡功能😋
近期架构高危漏洞较多 晚些可能会进行维护
沪港晚高峰体验4k秒开
Showing the 12 most recent of 29 posts we hold for @UeolyNetworkChannel. 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 8 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.
Named by
Channels on the register whose posts name this channel's handle.
@cloudtestcesu · 15,7162 posts品云☁️机场导航
@PinYunPs · 19,3012 posts山茶花の白嫖机场频道
@schpd · 18,6462 posts机场云 测速☁️频道
@yunspeedtest · 8,9892 posts某咕咕的 机场 & VPN 测评站
@AAAMouGuGuVPN2026 · 3,9261 post机场测速/推荐/观察
@duang_speedtest · 32,7591 post推个鸡场|优质小而美机场推荐
@PushGoodCloud · 13,6061 post小众机场测评
@sstrojan · 23,7401 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@UeolyNetworkChannel named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 15 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 November 2026 — this entry's latest reading, not the date you are reading this.
“UeolyNetworkCannel” (@UeolyNetworkChannel), 212 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/UeolyNetworkChannel.
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.