#网友曝光 缅东三佛塔黑园区 缅东三佛塔黑园区的几个黑管理,衍森,大志,锦陈,小浩,以上4个管理是贵州人。刘天也,江凡,啊杰,这3个是福建人,这7个管理。打死了2个中国人,园区大老板“文哥”福建人,公司700多个员工都是骗来的,买来的,还有未成年,这几个管理每个月拖欠工资和找员工借钱不还,每天工作16-18小时,睡觉睡办公室,没有休息。请有关部门尽快清扫缅东三佛塔黑园区,这一次曝光几个管理是提醒一下,下次直接曝光照片,照片准备好了。 这是公司一部分员工名单,最后请求园区物业,给我们员工联系一下家人,我们被买来三佛塔园区七八个月了,还没有联系家人。 ➡ 今日投稿 x 网友曝光 🤪 ➡️ 爆料投稿联系: @Kinki88 😀

Channel
今日投稿 x 网友曝光
@BCNEWS6
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003931038102 |
|---|---|
| Type | Channel |
| Username | @BCNEWS6 |
| Description | 报章上不会出现的新闻,专注于博彩最新动态资讯,生活故事分享,海外华人求助,曝光,让你看尽海外华人大小事 ✅ 灰产资讯 ✅ 安危事件 ✅ 曝光爆料 ✅ 时事新闻 ✅ 社会热点实时推送 |
| Created | 25 May 2026 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BCNEWS6 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 16:17 | 1 | no change |
| 8 Aug 2026, 13:01 | 1 | first reading |
Engagement
2 posts held, back to 25 May 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 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 2 posts for this entry, the most recent from 25 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 1
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
Channel created
Showing the 2 most recent of 2 posts we hold for @BCNEWS6. 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
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.
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.
“今日投稿 x 网友曝光” (@BCNEWS6), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/BCNEWS6.
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.