Channel
@xinwenTV5
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
8,510subscribers
-2,484 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001859396975 |
|---|---|
| Type | Channel |
| Username | @xinwenTV5 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/xinwenTV5 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 77% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 21:38 | 8,510 | -340 |
| 14 Sept 2026, 02:38 | 8,850 | -307 |
| 10 Sept 2026, 18:17 | 9,157 | -472 |
| 6 Sept 2026, 01:58 | 9,629 | -358 |
| 2 Sept 2026, 08:42 | 9,987 | -128 |
| 1 Sept 2026, 06:44 | 10,115 | -117 |
| 31 Aug 2026, 04:24 | 10,232 | -89 |
| 30 Aug 2026, 05:13 | 10,321 | -106 |
| 29 Aug 2026, 06:36 | 10,427 | -87 |
| 28 Aug 2026, 05:23 | 10,514 | -174 |
| 27 Aug 2026, 01:55 | 10,688 | -30 |
| 26 Aug 2026, 03:13 | 10,718 | -17 |
| 25 Aug 2026, 05:33 | 10,735 | -2 |
| 24 Aug 2026, 01:46 | 10,737 | -46 |
| 22 Aug 2026, 06:14 | 10,783 | -18 |
| 20 Aug 2026, 19:36 | 10,801 | -9 |
| 19 Aug 2026, 18:43 | 10,810 | -9 |
| 18 Aug 2026, 21:35 | 10,819 | -36 |
| 17 Aug 2026, 18:27 | 10,855 | -29 |
| 16 Aug 2026, 17:15 | 10,884 | first reading |
3 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 28 pages 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 3 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 3 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 11 June 2026 to 1 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#东南亚爆料 #赵倩 #扬州 #小三 #杭州 #浙江迈伺特智能装备有限公司 #市场部 #市场经理 浙江迈伺特智能装备有限公司 市场经理 职场越界，介入他人婚姻，女子遭原配公开曝光 原配实名曝光一起婚内情感纠纷。江苏扬州36岁女子赵倩，任职于浙江迈伺特智能装备有限公司的市场经理岗位，逾越职业与道德底线，不正当介入他人婚姻，破坏家庭稳定。 据原配阐述，赵倩长期与其丈夫保持不正当私密关系，日常频繁搭乘男方私家车，并多次发生不正当关系。原配直言，对方假借职场身份接触异性，借私密关系谋取私利，行为严重违背公序良俗。 原配已掌握涉事人员、其直系家属完整身份资料、常住地址及就职单位等信息，希望其家属约束赵倩的行为，及时止损，避免事态不受控制。同时正面警告当事人，若仍不知收敛，后续会采取进一步措施。 婚恋与职场边界感是人际交往基本准则，成年人理应恪守道德底线。美好生活是靠自己的双手奋斗出来的，而不是借助他人来满足自己贪婪的欲…
❤1
⚠️ 曝光无良黑平台！乐赢娱乐（Leying）直接跑路，吞员工血汗钱！ 平台：https://www.leying.fun/ 备用：https://leying.co/ 事情经过： 我在招聘群被乐赢娱乐招去当远程客服。一个自称IGM（号称主管）的家伙联系我，说招世界杯客服。 试用期要工资1000U 转正（1200U） 用小号 【乐赢商务】 TG：@LEYINGBC 邮箱：[email protected] 用了一个小号【乐赢商务】（TG: @LEYINGBC）来对接。期间这两个号二号同登，经常回错消息，其实我们心里都清楚是一个人在演双簧，但为了上班拿工资都忍了。我从5月底干到6月底，每天12小时夜班，以前做过客服组长，然后让我们写话术、写规矩演的很认真，拼命回客服、写话术。结果昨天突然解散所有工作群，IGM /乐赢娱乐直接把所有人拉黑！ 有人找他，他先狡辩说“不小心删记录”，第二天账号直接注销跑路！ 一个月血汗钱一分没发！ 听说还有代理…
新宝娱乐 只要拿家人 孩子发誓。或者证据 证人拿出来。42623这号上个月1-5号转移前（账目结给谁 结清了）如果拿不出来。你们就不要在这里脏水还往客户这破了。吃了便宜还卖乖。最喜欢占便宜的盘口。吃代理数据的盘口。新宝娱乐 玩家们 大家自己对比待遇 对比数据。是不是套路深 杀数最高，这种殇良心盘口，怎么玩的下去！颠倒是非。。他们就缺三瓜两枣。让新宝的会员们自己评理！做假账！ 你们说我吃股东拉富贵来玩的佣金，去尼玛的 他老婆还是我妹呢！只是不说让她赚点钱 代理费多给他结了，结果是你们以为我们吵架就从中做梗。42623号 负盈利不结 以为我们不知道！ 新宝娱乐。满满套路 满满杀猪味 吃人不吐骨头，希望公安部早点铲除这种势力！大家抵制黑平台！ xbyl.vip 新宝娱乐。 黑台子
Showing the 3 most recent of 3 posts we hold for @xinwenTV5. 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.
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.
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 47 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“新闻曝光/菲律宾曝光/黑平台曝光” (@xinwenTV5), 8,510 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/xinwenTV5.
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.