30 Dec 2025, 13:17 UTC2 viewsread 14 August 2026
拎料：https://t.me/SMVPACE 點上方鏈接加入👆👆
Channel
重心重注衝擊7連勝💥
@RWHRFDNVCNC
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 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 | -1003667301784 |
|---|---|
| Type | Channel |
| Username | @RWHRFDNVCNC |
| Description | 拎料：https://t.me/SMVPACE |
| Created | 18 December 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/RWHRFDNVCNC |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 08:47 | 1 | no change |
| 7 Aug 2026, 18:09 | 1 | first reading |
Engagement
8 posts held, back to 18 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 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 8 posts for this entry, the most recent from 30 December 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 6
Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
30 Dec 2025, 13:17 UTC2 viewsread 14 August 2026
拎料：https://t.me/SMVPACE 點上方鏈接加入👆👆
30 Dec 2025, 13:17 UTC2 viewsread 14 August 2026
拎料：https://t.me/SMVPACE 點上方鏈接加入👆👆
30 Dec 2025, 13:17 UTC2 viewsread 14 August 2026
拎料：https://t.me/SMVPACE 點上方鏈接加入👆👆
30 Dec 2025, 13:17 UTC2 viewsread 14 August 2026
拎料：https://t.me/SMVPACE 點上方鏈接加入👆👆
30 Dec 2025, 13:17 UTC2 viewsread 14 August 2026
拎料：https://t.me/SMVPACE 點上方鏈接加入👆👆
30 Dec 2025, 13:17 UTC320 viewsread 14 August 2026
亞冠精英 00:00 艾薩德 - 沙巴柏阿爾艾利杜拜 全場3/3.5大✅✅✅ 亞冠精英 02:15 伊蒂哈德 - 納薩夫 全場3.5細✅✅✅ 非洲盃 04:00 喀麥隆(中) - 加蓬 全場2/2.5細✅✅✅ 以盃 02:00 特拉維夫夏普爾 - 阿舒多 特拉維夫夏普爾-0.5/1✅✅✅ 意甲 03:45 比薩 - 祖雲達斯 祖雲達斯-1✅✅✅ 意甲 03:45 羅馬 - 熱拿亞 羅馬-0.5/1✅✅✅ 精揀重心衝擊6連勝💥 英超 04:15 阿仙奴 - 阿士東維拉 簡介重心有殺過無錯過💥 @SMVPACE 👈免費加入 @SMVPACE 👈免費拎料
18 Dec 2025, 03:47 UTCviews —
Channel created
Showing the 8 most recent of 8 posts we hold for @RWHRFDNVCNC. 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
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“重心重注衝擊7連勝💥” (@RWHRFDNVCNC), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/RWHRFDNVCNC.
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.