#阿联酋新闻:亚美尼亚与迪拜磋商跨境洗钱调查及资产追缴合作 亚美尼亚与迪拜检察机关代表在布宜诺斯艾利斯会面,磋商跨境洗钱、腐败案件的侦查协作与资产追缴事宜。 两国依托2002年签署的司法互助协议,计划优化协作流程、共享线索,提升追查和没收非法资产的效率,并同步推进引渡合作。
❤🔥4❤2🔥2🤩2🥰2🎉1👍1😍1

Channel
@Dubaihuarenzixun
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
62,672subscribers
-25,382 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001529684619 |
|---|---|
| Type | Channel |
| Username | @Dubaihuarenzixun |
| Description | 📣华人资讯,敢揭敢说,为民发声! ✍️投稿爆料: @DubaihuarenzixunBot 📡东南亚新闻导航: @HuarenZM 🍉搞笑吃瓜: @chigua_huaren_chigua 🤝求职&招聘:(免费发布) @Huaren_zhaopin_qiuzhi 📲商务合作: @Huaren01 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/Dubaihuarenzixun |
Gambling & betting — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
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 in near-verbatim form on 12 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 |
|---|---|---|---|
| @Dubai_xinwen/4601812 Oct 2026, 09:33 UTC | @Dubaihuarenzixun/68082 · this entry12 Oct 2026, 09:33 UTC | 1.00 | under a minute |
| @Dubai_xinwen/4606513 Oct 2026, 18:02 UTC | @Dubaihuarenzixun/68137 · this entry13 Oct 2026, 18:02 UTC | 1.00 | under a minute |
| @Dubai_xinwen/4616717 Oct 2026, 11:25 UTC | @Dubaihuarenzixun/68274 · this entry17 Oct 2026, 11:26 UTC | 1.00 | under a minute |
| @Dubai_xinwen/4643024 Oct 2026, 07:32 UTC | @Dubaihuarenzixun/68566 · this entry24 Oct 2026, 07:32 UTC | 1.00 | under a minute |
| @Dubai_xinwen/4648525 Oct 2026, 17:23 UTC | @Dubaihuarenzixun/68625 · this entry25 Oct 2026, 17:23 UTC | 1.00 | under a minute |
| @Dubai_xinwen/469619 Nov 2026, 10:23 UTC | @Dubaihuarenzixun/69211 · this entry9 Nov 2026, 10:23 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Dubai_xinwen | 266 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @Dubai_xinwen (259–7) |
| @dubai_xinbibaoguang | 266 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @dubai_xinbibaoguang (261–5) |
| @dubai_baoguang | 264 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @dubai_baoguang (259–5) |
| @feilvbinhuarenzixun | 28 (8/8 hand-verifiable sample passed) | 0.91 | under a minute | this entry (24–4) |
| @yinnihuarenzixun | 21 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @yinnihuarenzixun (21–0) |
| @laowohuarenzixun | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @laowohuarenzixun (16–2) |
| @malaixiyahuarenzixun | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @malaixiyahuarenzixun (18–0) |
| @yuenanhuarenzixun | 17 (8/8 hand-verifiable sample passed) | 0.98 | under a minute | @yuenanhuarenzixun (15–2) |
| @huaren_zixun | 14 (8/8 hand-verifiable sample passed) | 0.94 | under a minute | @huaren_zixun (12–2) |
| @taiguohuarenzixun | 13 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | this entry (12–1) |
| @miandianhuarenzixun | 12 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (11–1) |
| @jianpuzhaihuarenzixun | 11 (8/8 hand-verifiable sample passed) | 0.89 | under a minute | this entry (8–3) |
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. 879 of the 879 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 2,032 comparable posts for this entry, running 7 August 2026 to 17 November 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.
Of the group of 4 channels, the one whose matching posts we hold earliest is @Dubai_xinwen. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 18 November 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 is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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 |
|---|---|---|
| 17 Nov 2026, 11:20 | 62,672 | -777 |
| 14 Nov 2026, 01:20 | 63,449 | -871 |
| 11 Nov 2026, 06:39 | 64,320 | -284 |
| 9 Nov 2026, 10:09 | 64,604 | -324 |
| 7 Nov 2026, 23:01 | 64,928 | -164 |
| 6 Nov 2026, 18:18 | 65,092 | -137 |
| 5 Nov 2026, 16:01 | 65,229 | -81 |
| 4 Nov 2026, 18:09 | 65,310 | -169 |
| 3 Nov 2026, 17:11 | 65,479 | -580 |
| 2 Nov 2026, 20:41 | 66,059 | -363 |
| 1 Nov 2026, 22:27 | 66,422 | -131 |
| 31 Oct 2026, 23:49 | 66,553 | -217 |
| 31 Oct 2026, 00:06 | 66,770 | -312 |
| 30 Oct 2026, 01:19 | 67,082 | -533 |
| 29 Oct 2026, 03:50 | 67,615 | -217 |
| 27 Oct 2026, 23:46 | 67,832 | -136 |
| 27 Oct 2026, 00:20 | 67,968 | -129 |
| 26 Oct 2026, 00:10 | 68,097 | -123 |
| 24 Oct 2026, 21:16 | 68,220 | -261 |
| 23 Oct 2026, 17:56 | 68,481 | first reading |
3,363 posts held, back to 7 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 209 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 553 of 591 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 3,363 (7 August 2026 – 18 November 2026) |
| Views total | 1,952,723 |
| Reactions total | 9,026 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 09:12 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 180 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.
10,296 reactions across 622 posts, in 12 distinct kinds. The most used accounts for 11.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😍 | 1,199 | 11.6% | |
| 🤩 | 1,193 | 11.6% | |
| ❤ | 1,148 | 11.1% | |
| 🔥 | 1,146 | 11.1% | |
| ❤🔥 | 1,138 | 11.1% | |
| 💯 | 1,129 | 11.0% | |
| 🥰 | 1,116 | 10.8% | |
| 👍 | 1,107 | 10.8% | |
| 🎉 | 1,106 | 10.7% | |
| 👏 | 5 | 0.049% | |
| 😁 | 5 | 0.049% | |
| ⚡ | 4 | 0.039% |
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 622 of the 1,000 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 10,296 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 15 October 2026 to 18 November 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.
Telegram’s own ‘edited’ marker: 0 of 886 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#阿联酋新闻:亚美尼亚与迪拜磋商跨境洗钱调查及资产追缴合作 亚美尼亚与迪拜检察机关代表在布宜诺斯艾利斯会面,磋商跨境洗钱、腐败案件的侦查协作与资产追缴事宜。 两国依托2002年签署的司法互助协议,计划优化协作流程、共享线索,提升追查和没收非法资产的效率,并同步推进引渡合作。
❤🔥4❤2🔥2🤩2🥰2🎉1👍1😍1
#阿联酋新闻:迪拜警方捣毁投资诈骗团伙,利用银行卡和数字钱包转移赃款 迪拜警方捣毁一个投资诈骗犯罪团伙。该团伙招募人员办理银行卡和数字钱包,随后收走账户控制权,用于转移诈骗赃款,以此规避资金追踪。 警方已实施抓捕,并提醒公众切勿出售或出借个人账户,以免卷入洗钱案件并承担刑事责任。
😍4❤2🎉2🔥2🤩2🥰2👍1
#阿联酋新闻:每月最低缴纳5迪拉姆,失业可领多少?9个月向2.8万人赔付2.5亿迪拉姆 阿联酋的失业保险计划在2026年前九个月交出了一组数据:约28,000名失业劳动者获得了超过2.5亿迪拉姆的赔偿金。 阿联酋人力资源与酋长国化部(MoHRE)近日通过数字平台发布声明,公布了这组数据。自2024年“非自愿失业保险计划”(ILOE)启动以来,累计赔付总额已超过6.2亿迪拉姆。目前,该计划覆盖了私营部门93%的目标劳动群体。 每月最低缴纳5迪拉姆,换的是什么? 这是一项由政府与私营部门合作实施的强制性保险计划。其基本机制是:员工在职期间缴纳少量保费,一旦因非自愿原因失业,在找到新工作之前,可以获得一笔临时经济援助。 保费根据基本工资分为两档: 第一类:月基本工资在16,000迪拉姆及以下的员工,必须参加第一类保险,每月保费为5迪拉姆(不含增值税)。 第二类:月基本工资超过16,000迪拉姆的员工,属于第二类保险,每月…
❤3❤🔥3🥰3👍2😍2🎉1💯1
#阿联酋新闻:阿布扎比斗殴案8名涉案人员获减刑,每人缴纳15万迪拉姆罚款 阿布扎比刑事法院近日对8名涉案人员的刑期作出减判。这些人此前因参与群体性斗殴、拍摄斗殴过程以及在酒店内制造骚乱而被定罪。该事件起因于涉案人员之间此前存在的纠纷。 根据修订后的裁决,每名被告均须缴纳15万迪拉姆罚款。 此次作出减判,是因为涉案各方已经达成和解,并相互撤回诉求。此外,受害者也向阿布扎比政府提出请求,希望释放这些被告。 该裁决体现了既定的法律程序,并综合考量了案件的司法评估结果。法院在审理过程中,充分考虑了各方达成的和解协议,以及当事人同意放弃各自针对该事件提出的诉求。 此前,刑事法院认定,其中6名被告犯有扰乱公共秩序、制造恐慌以及危及他人生命安全等罪行;其余2名被告则因拍摄斗殴过程,并将相关视频发布到网络平台而被定罪。
😍3❤🔥2👍2💯2🔥2🥰2❤1🎉1
#阿联酋新闻:迪拜女子以70万迪拉姆出售假百达翡丽,遭罚款并被判全额退款 一块假表,卖了70万迪拉姆。买家原以为购买的是真品百达翡丽,直到发现手表是假货后报警。 迪拜轻罪法院近日对这起案件作出判决:涉案女子因将假冒百达翡丽手表当作真品出售,被处以1万迪拉姆罚款。法院同时下令没收涉案手表,并要求她向买家退还70万迪拉姆购表款。 法院认定,买家在手表真伪问题上受到误导,涉案款项系通过欺诈手段获取。相关判决涉及三个方面:罚款属于刑事惩罚,没收用于清除假冒商品,退款则是返还通过欺诈手段获取的钱财。 上诉被驳回,再上诉仍被驳回 该女子曾就判决提出上诉,但遭到驳回,原判决得以维持。随后,她又向最高法院提起上诉,再次被驳回。至此,刑事判决正式生效。 刑事程序结束后,买家针对自身经济损失提起民事诉讼。迪拜民事法院判令该女子退还70万迪拉姆,并自民事判决之日起,按照每年5%的利率支付法定利息,直至全部款项付清。 此外,她还被判承担法…
💯3❤2❤🔥2🎉2👍2🔥1🤩1🥰1
迪拜新闻|华人资讯曝光|dubai news pinned a video
🎮🎮🎮🎮😀😃😄😁😆 👹👺🤡💩🤯😳🥵🥶 🔥 汇聚全球热门电子游戏 ⚡️ 各大百家乐平台齐全 💥 游戏体验感全网第一 TG老台全网零曝光,只做实力 🏆3月某盘口老板当天提现63万T 🏆3月某盘口老板再次实力喜提350万T 🏆3月某会员充值50000U提现2700000U 💎 储备金亿U · 实力护航 · 长久稳定运营「点击验证」 点击有惊喜 1⃣ 笔笔送3%,实时返水3.0,Usdt+支付宝+各大钱包+okpay存款方便秒上分 2⃣代理流水(日结)+负盈利55%双抽模式零风险 3⃣每日盈利亏损大赠送独创U+人民币双系统等全网福利最高上R提U 🧐🤩🥳🥴 : 86.net 🎵🎶➕➖ : @KF86 😏😭🤯🤭 : @ytgj9999 😊🤣😆🫠 : @uu886bot 😀点击注册 : 「USDT」 「人民币」 ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡⚡⚡🤓🤓🤓🤓🤓🤓🤓
🤩4🎉3💯2🔥2🥰2❤1😍1
没人会爱上纯粹的你,每个人都会衡量你的价值 🤩搞笑吃瓜👉点击进入 🧐新闻曝光导航 🔵商务合作/爆料投稿: @Huaren01
❤🔥3🔥3😍3👍2💯2🎉1🥰1
迪拜新闻|华人资讯曝光|dubai news pinned a video
😎😎😎😎😎 😎 😎😎😎😎😎😎😎 😎↖😎😎😎😎😎😎🛍😎😎😎 🌐 亿级域名|2G.COM 品牌定位全球 实力超乎想象 全网福利天花板 入款笔笔送3%无上限 全网召集【老玩家入驻】VIP等级1:1平移 同行文案写的天花乱坠 不如2G的U到位 全球布局 · 100%保障出款 · 秒充秒提 💥新人超会赢,精彩时刻分享: 😎 PG电子 新玩家游戏中爆出160万U大奖,本金仅用8000U 😎😎😎 😎 DB真人 玩百家乐的老板,第一天存款66万U,提款680万U 😎😎😎 😎😎😎😎: 2g26.cc 🛍🛍🛍😎: @GF2Gcom 🥰领🥰会员 😎😎😎😎: @KF2Gcom 😎😎😎😎: @DL2Gcom 😎😎😎😎: @sx2ggbot 😎😎😎😎🛍😎😎😎 😎😎😎😎😎😎😎😎😎😎
👍3🤩3❤🔥2🔥2❤1🎉1💯1🥰1
迪拜新闻|华人资讯曝光|dubai news pinned a video
😃😃😃😃 😃😃😃😃😃😃😃 😃😃😃😃😃😃😃😃 😍8G国际娱乐 华人最稳首选🔤台 😍顶级团队,重金打造,铸造行业标杆 😍视讯全网最高反水🇹🇬%,输赢双边计算反水 😍加拿大PC28综合U台最高赔率,输赢双边计算反水 🥰☺🥲😊😇 🩷活动救援金、亏损金、返佣金、充值金、闯关奖、充值额外奖、周福利、月福利,频道每日🇺🇸个红包 🐙储备金上亿U 头部担保 大玩家最稳首选! 😘 真人视讯😘😘万U一口 😘 PG电子麻将糊了😘😘😘😘U一拉 🐙 大玩家聚集地 大额秒出款 🩷🩷🩷🩷🩷🩷🩷 🩷🩷🩷🩷🩷🩷🩷 最稳大平台,点击以下链接认证 👇 😍世博联盟-联盛担保1000万U 😍okapy钱包-ok28担保上押300万U 😍8G国际娱乐官方福利群 公开透明 😃😃😃😃😃:8G.COM 😃😃😃😃😃: @KF8G 😃😃😃😃😃: @TG8G 😃😃😃😃😃: @GF8G
❤🔥4🤩3❤2🥰2🎉1💯1🔥1😍1
Showing the 12 most recent of 3,363 posts we hold for @Dubaihuarenzixun. 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 3 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 18 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 57 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 November 2026 — this entry's latest reading, not the date you are reading this.
“迪拜新闻|华人资讯曝光|dubai news” (@Dubaihuarenzixun), 62,672 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/Dubaihuarenzixun.
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.