11 Jun 2026, 05:18 UTC35 viewsread 8 August 2026
Video
@Hotchigua 6月11，凌晨 ，西班牙马德里- 唐人街usera，夜晚突发持刀伤人事件，同胞们夜晚最好不要出门，保护好自己跟家人。
Channel
香港吃瓜娱乐
@tw28cg
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
715subscribers
-18 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003442785668 |
|---|---|
| Type | Channel |
| Username | @tw28cg |
| Description | ➡️加入香港28集团，畅享豪华大奖，开启财富之旅👈 🔔官方网址: xg28.app 🔔精准预测网: xg2888.cc 🔔六合论坛: xg49.tv 🔔比分网: xg999.vip 🔔66吃瓜: xg666.tv 🔔精字窝: jzw01.cc 🔔TG官方群: @xg28cc 🔔TG体育频道: @hk28cc 🔔TG客服: @xg28tv 🔔心舟客服: XG8888 🔔心舟下载地址: xz333.com 🔔在线客服: xg2828.com |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/tw28cg |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:16 | 715 | no change |
| 8 Aug 2026, 01:43 | 715 | -18 |
| 7 Aug 2026, 23:03 | 733 | first reading |
Engagement
7 posts held, back to 11 June 2026 — 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 pageof 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 7 posts for this entry, the most recent from 11 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈1,540
- Videos
- ≈4,120
- Links
- ≈65
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 2s
- Average length
- 1s
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
11 Jun 2026, 05:18 UTC36 viewsread 8 August 2026
Video
@Hotchigua 6月10日 山西一段盘山公路上，一队摩托车结伴行驶，途中和一辆轿车迎面会车，在交错通行过程中，其中一辆摩托车意外跌落山崖。 现场拍摄人员表示，万幸骑手并无大碍。 ★……
11 Jun 2026, 05:17 UTC35 viewsread 8 August 2026
Photo
@Hotchigua 肉偿租房🥸
11 Jun 2026, 05:17 UTC19 viewsread 8 August 2026
Photo
@Hotchigua 肉偿租房🥸
11 Jun 2026, 05:02 UTC18 viewsread 8 August 2026
Video
@Hotchigua 日前被柬埔寨警方逮捕的柬埔寨安徽（总）商会会长刘忍，6月10日已由柬方移交中国警方，并被押解返回中国。6月5日，刘忍在金边黄山国际大厦47楼被柬埔寨执法部门带走。据悉，刘忍在柬埔寨被捕，因涉及跨境资金洗白、电信网络诈骗、非法人口转运等多项跨国违法犯罪行为。
11 Jun 2026, 04:47 UTC15 viewsread 8 August 2026
Video
@Hotchigua 监控一幕 戴着眼镜斯斯文文，狠起来自己都不放过 眼镜一戴，谁都不爱，但狠起来自己都不爱
11 Jun 2026, 04:47 UTC14 viewsread 8 August 2026
Photo
@Hotchigua 补充😱
Showing the 7 most recent of 7 posts we hold for @tw28cg. 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 — 709,745 of 1,160,990entries 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.
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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“香港吃瓜娱乐” (@tw28cg), 715 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/tw28cg.
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.