Channel
@miandianQ
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
11,128subscribers
-44,523 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002481665575 |
|---|---|
| Type | Channel |
| Usernames | @jinsanjiao @miandianQ |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/miandianQ |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 8 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @miandianQ/58010 · this entry6 Aug 2026, 13:21 UTC | @yuenanU/577956 Aug 2026, 13:25 UTC | 1.00 | 5 minutes |
| @yuenanU/578076 Aug 2026, 14:01 UTC | @miandianQ/58022 · this entry6 Aug 2026, 14:01 UTC | 1.00 | under a minute |
| @miandianQ/58025 · this entry6 Aug 2026, 14:58 UTC | @yuenanU/578106 Aug 2026, 14:59 UTC | 1.00 | 72 seconds |
| @miandianQ/58032 · this entry6 Aug 2026, 15:40 UTC | @yuenanU/578176 Aug 2026, 15:41 UTC | 1.00 | 72 seconds |
| @miandianQ/58153 · this entry7 Aug 2026, 11:58 UTC | @yuenanU/579417 Aug 2026, 11:58 UTC | 1.00 | under a minute |
| @miandianQ/58176 · this entry7 Aug 2026, 14:13 UTC | @yuenanU/579647 Aug 2026, 14:16 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @yuenanU | 24 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (19–5) |
| @yuenanE | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (14–4) |
| @chiguak | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (13–4) |
| @xigangz | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (13–4) |
| @Bx666x | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Bx666x (11–6) |
| @jinbiany | 13 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (11–2) |
| @dibaif | 11 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (11–0) |
| @baoliaoc | 8 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (8–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 30 of the 30 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 42 comparable posts for this entry, running 6 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 9, the earliest publisher we hold is @miandianQ — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 8 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 12:58 | 11,128 | +1,295 |
| 19 Sept 2026, 02:37 | 9,833 | -1,452 |
| 17 Sept 2026, 04:41 | 11,285 | +877 |
| 16 Sept 2026, 19:36 | 10,408 | -1,359 |
| 15 Sept 2026, 04:56 | 11,767 | -1,311 |
| 14 Sept 2026, 20:59 | 13,078 | +596 |
| 13 Sept 2026, 11:16 | 12,482 | -611 |
| 13 Sept 2026, 04:40 | 13,093 | -1,465 |
| 11 Sept 2026, 14:21 | 14,558 | +1,424 |
| 11 Sept 2026, 05:17 | 13,134 | -4,736 |
| 8 Sept 2026, 23:01 | 17,870 | +4,690 |
| 8 Sept 2026, 07:59 | 13,180 | -6,939 |
| 5 Sept 2026, 12:20 | 20,119 | -599 |
| 3 Sept 2026, 16:17 | 20,718 | +7,484 |
| 2 Sept 2026, 07:24 | 13,234 | -7,958 |
| 2 Sept 2026, 05:28 | 21,192 | -933 |
| 1 Sept 2026, 08:44 | 22,125 | +8,839 |
| 1 Sept 2026, 06:13 | 13,286 | -9,810 |
| 31 Aug 2026, 10:25 | 23,096 | +9,761 |
| 31 Aug 2026, 09:38 | 13,335 | first reading |
240 posts held, back to 6 August 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 24 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 240 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 86 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.
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 4 of the 240 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 240 most recent posts we hold, published 6 August 2026 to 15 August 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.
🇵🇰 伊斯兰堡斯被抓狗推反馈： 巴基斯坦警察雇佣本地人进入大楼。带着面具，手持铁棍要对里面的人进行殴打。强迫他们签署犯罪文件。 目前大楼里面的人要求律师出门，本地警察不予理会，请中国和越南大使馆关注此事件！ “我们需要依法维护自己的合法权益。过去几天，我们遭受了许多不公平、不合理的对待，现在我们要求相关方面尊重并保障我们的基本权利。 我们正式要求尽快归还被扣留的手机、护照以及其他个人物品和证件，并保障我们能够正常与家人及外界取得联系。同时，我们要求获得律师的法律协助，以确保后续所有程序依法、公正、透明地进行。 我们愿意依法配合必要的调查和程序，但我们的合法权益同样必须得到充分尊重和保障。 我们希望通过合法途径解决问题，并要求停止任何不公正或不合理的对待。” 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888
🇵🇰 伊斯兰堡斯帕科广场“Sparco Plaza大楼”372名狗推被抓案件进展 综合多家巴基斯坦媒体报道： 8月12日，巴基斯坦FIA、NCCIA联合突击伊斯兰堡斯帕科广场，一共抓获372名外籍人员，分两起案件立案。 1. FIA（联邦调查局）抓获258人（其中包含中国籍，印尼籍，马来籍，越南籍等）：该批人员持旅游、访问、商务签证入境，涉嫌在当地运营呼叫中心，从事签证许可范围以外的经营活动，依据《外国人法案》立案。 2. NCCIA（网络犯罪调查局）抓获114人（111名中国籍、3名越南籍）：涉嫌运营网络网恋色情敲诈团伙，通过网络色情聊天录制视频，以此要挟受害人索取钱财，依据《预防电子犯罪法案》立案。 8月13日，当地政府将斯帕科广场划定为临时分监狱，全部嫌疑人就地关押，由FIA与当地警方共同安保。 据当地媒体报道，办案现场查获大量电子作案设备，搜出仿制越南执法机构制服、印章。 经过进一步审讯排查，在全部在押人员当…
❤1
#群友投稿：东南亚：一场关于机会与命运的远行 从古至今，大多数人都逃不过一种“病”——穷病。很多人会问，明明每个人都有能力，为什么还会陷入贫穷？ 因为这个世界，从来不是只有能力就足够。能力人人都有，但机会并不是人人拥有。 在这个人口拥挤、竞争激烈的时代，资源被不断分割，岗位被不断挤压，收入被不断降低。很多人拼尽全力，却依然只能站在原地。不是不努力，而是时代的洪流太快，普通人的脚步太慢。 于是，从此踏上了东南亚的土地。为了梦想，为了一夜翻身，为了只是想寻找一个改变人生的机会。来到这里，进入陌生的城市，做着曾经想不到的工作——灰产 追逐的，其实不是所谓的“暴富”，而是一个机会。一个能让自己翻身的机会。 曾经的东南亚，被很多人看作一片充满可能的土地。这里有新的城市，有快速发展的经济，有别人眼中的“财富窗口”。互联网让世界变得透明，让普通人看到了另一种生活，也让无数人幻想着有一天能够拥有财富、自由和体面的未来。 物以稀为贵…
网友：我要曝光这个完美傻逼公司、提成不发 、工资全部扣除我 、还要让我倒贴450U，比杀猪盘还坑 赔付单没有发给我看、直接全部扣除、一份钱都没有、人家公司人选跳票是有名额 可以免赔付 、或者赔付 一半 。这里 全部招聘承担 、我就是要全部承担 1350U人选跳票上个月的事、广告费也要赔付、公司说要查后台数据、商家跑路了 、现在都算我的赔付头上、广告费又赔付 150$ ， 其他公司都不用查后台数据。没有完成任务 就 扣 2000 人民币。完成任务都不发提成！什么鬼公司啊？ 8 月 6 号 晚上 22:00 多 就发通告辞退我们、通告就说 8 月 15号 会算工资、提成给我们 ，结果到了 8 月 15 号 、我的工资条是 还要倒贴 450u给公司 、在提成扣除。我的 6 月提成 都不发给我、一直画大饼、这个饼越画越大。找了公司的老板 、一个是人资主管、一个是公司老板、反馈事情、最后得到的回复是说、我们都按上面领导办事、我们不知道。…
网友：近期出门的兄弟都怎么样顺利吗 我兄弟上海出来被卡关了，手机被海关拿走十多分钟也不知道拿去干嘛了，后面安排走广州那边凌晨5点的机票，走的自助也有人被拦下来，七八个自助通道，两边站了十多个警察，有没有近期出来的，说说情况 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888
#缅甸资讯：泰昌园区周六夜部分熄灯，仍有大范围亮灯，消息称部分人员正转移 8月15日晚，位于缅甸一侧、泰国达府朴帕县邦卡本村对岸的泰昌园区出现部分区域熄灯、整体亮度下降的情况。现场观察显示，部分建筑已经关闭灯光，但园区中心的大型建筑群仍保持较为明显的照明，园区并未出现整体停运或完全熄灯的迹象。 泰昌园区此前被多方指认为缅甸克伦邦考克特区主要诈骗园区之一。近期，随着当地军事压力及武装冲突加剧，园区及周边安全形势持续受到关注。 据现场消息，近期已有部分人员及相关运营活动陆续向其他地点转移。不过，目前尚无法仅凭夜间灯光变化判断园区内部具体运营情况，也无法据此确认相关诈骗活动是否仍在持续。 从8月15日晚的现场情况来看，泰昌园区部分楼栋虽已熄灯或降低照明强度，但仍有相当数量的建筑保持亮灯，园区整体仍具有明显的人员及运营活动迹象。 现场位置：泰国达府朴帕县邦卡本村对岸、缅甸一侧泰昌园区。 👉东南亚大事件: @kk888 👉东…
#群友投稿：当代人的一种苦：拼尽全力，却依然被生活推着走 这一代人的苦，不是不努力，而是努力之后，依然很难改变自己的处境。谁没有梦想？曾经的我们，也想拥有更好的生活，也想靠自己的努力改变命运，也曾相信只要努力，就能换来未来。 每天早出晚归，用时间换工资，用身体换收入，可面对不断上涨的生活成本，很多人的努力最后只是勉强维持生活。资本的压力像一座无形的大山，企业追求更高的利润，员工却承担着越来越大的压力，加不完的班、降不下来的房租、越来越高的消费，让很多普通人感觉自己永远在追赶，却始终追不上。 把最好的几年交给工作，却发现收入增长赶不上现实变化。为了生存放弃梦想，为了一份工资忍受委屈，在日复一日的疲惫中慢慢失去了对未来的期待。 选择背井离乡，来到东南亚，幻想这里有新的机会，可以重新开始，可以改变人生。然而后来才发现，换了一片土地，并不一定能改变命运。在陌生的国家里，依然有人每天拼命工作，依然承受压力，依然为了生活苦苦坚持。 …
To哥最新出镜，依然精神矍铄，稳得一匹～～ 美国新大使要来了，是龙也得盘着，是虎得趴着，拿To哥毫无办法。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888
#群友爆料：泰缅边境大型诈骗园区“瑞当尼”，也称“新天地园区”。 目前园区内人数约1700人左右，加上缅甸当地服务人员以及后勤人员，总人数大约在2200人左右。 园区内部安保森严，基本上每隔10米左右就有一名保安巡逻。园区内中国人、越南人居多，目前大约有10个小公司。其中，C1、C2办公室被认为是最黑的区域。 打骂、体罚只是最基本的手段，员工多次向物业反映情况后，不但没有改善，反而变本加厉。这些公司主要从事国内精聊盘口业务。 相关管理人员包括：老板：阿健。大主管：罗峰。主管：阿吉、川杰。后勤：阿生。组长：阿勇、小胡、阿墨、土炮、阿乐、大东（曾在“大魔神”出来）。你们继续作恶，不是不报，只是时候未到。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888
柬警方再澄清：印尼查获的1.3吨藏毒大米袋并非出自柬埔寨 针对印尼此前查获1.3吨用柬埔寨大米袋包装的氯胺酮案，柬埔寨肃毒局局长肯萨拉表示，经查该批毒品并非来自柬埔寨，系贩毒集团栽赃。 柬警方指出，该批毒品源自“金三角”，经泰国海域运往印尼。毒贩所用的柬文米袋或购自柬泰边境，或在泰国印制，意在嫁祸柬埔寨。 此前，印尼警方在一艘从泰国出发的货船上查获这批价值约1.16亿美元的毒品，并逮捕8名船员（7名缅甸籍、1名台湾籍）。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888
#巴基斯坦：拉瓦尔品第被围园区后续报道。 调查出现重大转折，官员称从中国和越南公民身上搜出与中国和越南警察制服。当局正在调查这些制服为何会出现在他们手中以及可能的使用方式。 ps：国内军包 这种回去基本上不会低于2年刑期 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888
#泰国新闻 泰南苏梅岛大规模“清网”！60家公司被查，62名外国人遭逮捕令 泰国头条新闻社讯 8月15日，泰国内政部副部长帕利皮，联合国家警察副总长萨兰、素叻他尼府府尹、商业发展厅及特别案件调查厅等部门，出动超过300名执法人员，在苏梅岛县展开“捣毁外国人名义持股网络第7阶段”大规模行动。 此次行动旨在落实政府严厉打击外国人非法经营，以及利用泰国人代持股份、代管资产等违法行为的政策导向，重点查处外国资本通过“名义持股”方式规避法律、控制企业经营及土地资产的行为。 初步调查显示，涉案公司约60家，业务范围涵盖托儿所、豪华泳池别墅及签证服务等，涉及价值数十亿泰铢的土地资产。目前，法院已对62名外国人发出逮捕令。 此次行动系基于“帕岸岛模式”展开的延伸调查。执法人员对苏梅岛全部12,906家法人企业进行审查，发现其中8,254家存在外国股东，另有875家公司具备“名义持股”嫌疑。 经进一步深入筛查，执法人员锁定59家涉嫌违…
Showing the 12 most recent of 240 posts we hold for @miandianQ. 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.
Named by 11 registered channels — 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“金三角特区 亚太新闻 缅甸新闻” (@miandianQ), 11,128 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/miandianQ.
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.