Channel
@CCTV70
On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
290subscribers
-13 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001686233030 |
|---|---|
| Type | Channel |
| Username | @CCTV70 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/CCTV70 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 03:00 | 290 | -3 |
| 28 Aug 2026, 22:33 | 293 | -6 |
| 22 Aug 2026, 00:37 | 299 | -4 |
| 15 Aug 2026, 16:48 | 303 | no change |
| 14 Aug 2026, 13:30 | 303 | first reading |
5 posts held, back to 5 November 2024 — 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 5 posts for this entry, the most recent from 19 January 2025. An engagement rate over an empty window would be a number about nothing.
7 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🎉 | 3 | 42.9% | |
| ❤ | 2 | 28.6% | |
| 👍 | 2 | 28.6% |
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 5 of the 5 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 5 November 2024 to 19 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
钻石大厦 Century Diamond Tower树叶 ＃ ＃畅游 ＃AOA 钻石15楼 李鹭 树叶 @shuye11 你喜欢跑路，不出面解决问题，上个月月初你联合别人举报公司的事情还没有暴雷吧，还给人麻将馆一起搞了，后面跑我钱，跑这么快是怕公司找你吗？钱有这么好拿，那你就躲着在东南亚吧，殊不知你得罪很多人，回去蹲监狱吧，公司的名单不建议在发出来吧 15578503375 罗进远 18385999615 陈超毅 13885950808 夏思琴 18245424554 于建男 [email protected] 胡晓 15943764355 苏立娟 15241999502 孟皎 17300281717 董渲 15820797460 曾娟娟 17665331307 孙炜 13928284019 王乐 15761455608 毛保平 17321938153 付林霄 15266652193 陈瑞瑞 …
🎉3
#网友投稿 #曝光此人在 #钻石大楼15楼 #畅游 上班，换汇骗我90万p 骗子 #树叶 @shuye11 他在公司名叫 #网友 白马会账号 BMHB35922 ，他本人还欠我17万p，联合公司的人坑我90万p， 17号打完钱后，还去makati Air 在我朋友那边拿走一笔16万p，携款跑路 当天通过好友锁定他家里住址，大晚上我去抓人无果，他和小菲女友也都一起消失了，他告知我他上了飞机让不要我找他了 树叶你他妈的只会躲是吧？ #你给公司人换钱的手机号账号 有几十个电话号吧，？我都有， 你最好联系我
👍1
#网友投稿 #抢劫13万P 昨晚9点左右在马卡蒂蟹老头附近三叉路口，被4个小菲抢劫，我看见小菲掏枪我就跑了，我犹如博尔特附体，光速奔跑，不小时摔了一跤，导致手破皮。 我朋友当时在玩手机没注意，反应过来的时候已经被2把手枪指着头，当时我朋友背着包，只能老老实实的给他，包里现金13wp，外加9g工签，菲律宾马上过年了，大家一定要小心
👍1
#突发新闻 #抢劫 昨晚凌晨12.30分，在嘿网吧上网突然2个小菲拿着枪进来抢劫，抢了起码3个中国人的手机，一开始手机放在桌上有个小菲走过来直接拿走，我还没反应过来，马上去跑去把手机抢回来了，结果把他得手机也抢来了😂，然后小菲的另外一个同伙在门口放风，直接递了把枪给他，又走回来拿枪指着我，我当场吓蒙，把手机还给了他，还把身上的2000p也给了他，他妈的，现在想想真是吓死人
#网友曝光 #白马会 #白马会黑我79.2万P血汗钱，申诉迟迟得不到答复 2024年10月3日18:10 客户通过联系告知我，其给本人的白马会账户转账79.2万披索以换取USDT。 2024年10月3日晚22:10 白马会客服致电本人，通知这一笔款项是骗子通过各种手段从他人手中骗取的，本人配合白马会的工作人员，提供对应信息以协助调查。 2024年10月5日早10:00 本人白马会账户余额3561561全部冻结，且白马会官方在此之前未给出任何通知。同时，本人账户疑似被透露给了第三方。 2024年10月7日早10:20 白马会给本人的解决方案是：本人承担这笔金额的损失，退还给受害方79.2万P，以此来获得解封账户3561561余额冻结。 USDT和披索互换，本就是薄利多销的行业，这一笔挣钱都不到2000p,白马会直接冻结全部资金。 持续至今一个多月，白马会没有任何管理层的人员主动联系过本人，始终只有前台客服联系，并且只能得到官…
❤2
Showing the 5 most recent of 5 posts we hold for @CCTV70. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“东南亚新闻丨头条事件” (@CCTV70), 290 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/CCTV70.
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.