Channel
@lvyoue
On this record: Growth · Engagement · Posts · Citations · Cite this entry
13,102subscribers
-161 since we began measuring on 9 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002364294365 |
|---|---|
| Type | Channel |
| Usernames | @huwai @lvyoue |
| Created | 18 February 2025 — measured — dated from the channel’s first post |
| First recorded | 9 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/lvyoue |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 05:37 | 13,102 | -43 |
| 16 Sept 2026, 22:42 | 13,145 | no change |
| 16 Sept 2026, 20:56 | 13,145 | -21 |
| 15 Sept 2026, 01:42 | 13,166 | no change |
| 14 Sept 2026, 21:37 | 13,166 | -13 |
| 13 Sept 2026, 08:01 | 13,179 | no change |
| 13 Sept 2026, 04:39 | 13,179 | -34 |
| 11 Sept 2026, 09:22 | 13,213 | no change |
| 11 Sept 2026, 08:40 | 13,213 | -50 |
| 9 Sept 2026, 08:22 | 13,263 | no change |
| 9 Sept 2026, 07:47 | 13,263 | first reading |
2 posts held, back to 18 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 2 posts for this entry, the most recent from 10 May 2025. An engagement rate over an empty window would be a number about nothing.
✅欢迎来到西湖集团旗下看片频道 柬埔寨西湖集团联合通宝集团.迪威集团.铂莱集团.亨利集团.投资1000亿美金打造全球首家给赌博客户交社保.你来西湖娱乐.西湖给你养老.社保中心即将开启.@shebao 西湖集团.@xihu 柬埔寨西湖集团即将开启免费社区 免费看片 免费团饭 免费扶持 等一系列政策永久id.@mianfei 龙争虎斗彼岸花西湖给你一个家 无人扶我青云志西湖助我至山巅 继续观看 姐弟乱伦👉进入观看👈
Channel created
Showing the 2 most recent of 2 posts we hold for @lvyoue. 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.
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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“海角户外@huwai” (@lvyoue), 13,102 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/lvyoue.
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.