Channel
@liuhecai233
On this record: Growth · Engagement · Posts · Citations · Cite this entry
216subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002647286304 |
|---|---|
| Type | Channel |
| Username | @liuhecai233 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 4 times, most recently 1 September 2026 |
| On Telegram | t.me/liuhecai233 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 02:32 | 216 | no change |
| 11 Aug 2026, 07:16 | 216 | first reading |
13 posts held, back to 29 August 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 13 posts for this entry, the most recent from 14 March 2026. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
0️⃣【开云体育-澳门六合彩推荐】 开奖日期:2025/09/02 (2025245期)
中国福利彩票“快乐8”第2025233开奖公告 #开奖公告 #快乐8
中国福利彩票“3D”第2025233开奖信息 #开奖公告 #3D
中国福利彩票“双色球”第2025100期开奖公告 #开奖公告 #双色球
中国福利彩票“3D”第2025231期开奖信息 #开奖公告 #3D
0️⃣【开云体育-福彩3D推荐】 开奖日期:2025/08/31 (2025233期)
中国福利彩票“快乐8”第2025231期开奖公告 #开奖公告 #快乐8
中国福利彩票“3D”第2025230开奖信息 #开奖公告 #3D
中国福利彩票“双色球”第2025099期开奖公告 #开奖公告 #双色球
香港六合彩_第2025094期开奖信息 #开奖公告 #香港六合彩
0️⃣【开云体育-福彩3D推荐】 开奖日期:2025/08/30 (2025232期)
Showing the 12 most recent of 13 posts we hold for @liuhecai233. 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“香港六合彩|澳门六合彩” (@liuhecai233), 216 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/liuhecai233.
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.