Channel
@hyxw6
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
76,379subscribers
+42,579 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002175815388 |
|---|---|
| Type | Channel |
| Username | @hyxw6 |
| Description | ✅迪拜新闻头条，疑难杂症来问我 ✅本频道只负责相关发布信息，真假自行甄别！ ✅为全球华人分享迪拜文化，一起看最美的迪拜！ 投稿、合作： @feihang |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/hyxw6 |
National news — 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 61% 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 10 other registered channels. This entry also sits inside a group of 8 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 |
|---|---|---|---|
| @hyxw6/61824 · this entry10 Aug 2026, 08:17 UTC | @hyxw4/7136810 Aug 2026, 08:17 UTC | 1.00 | under a minute |
| @hyxw6/64185 · this entry31 Aug 2026, 13:50 UTC | @hyxw4/7372931 Aug 2026, 13:50 UTC | 1.00 | under a minute |
| @hyxw6/64678 · this entry5 Sept 2026, 05:08 UTC | @hyxw4/742225 Sept 2026, 05:08 UTC | 1.00 | under a minute |
| @hyxw6/65702 · this entry14 Sept 2026, 07:39 UTC | @hyxw4/7524614 Sept 2026, 07:39 UTC | 1.00 | under a minute |
| @hyxw6/66298 · this entry19 Sept 2026, 13:39 UTC | @hyxw4/7584219 Sept 2026, 13:39 UTC | 1.00 | under a minute |
| @hyxw6/66610 · this entry22 Sept 2026, 10:47 UTC | @hyxw4/7615422 Sept 2026, 10:47 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @hyxw4 | 798 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (797–1) |
| @hyxw3 | 723 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @hyxw3 (716–7) |
| @hyxw2 | 694 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (693–1) |
| @hyxw7 | 316 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @hyxw7 (307–9) |
| @hyxw8 | 243 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @hyxw8 (238–5) |
| @dnysj | 217 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @dnysj (213–4) |
| @hyxw5 | 121 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @hyxw5 (116–5) |
| @hyxw9 | 49 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (43–6) |
| @MB104 | 12 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | @MB104 (12–0) |
| @uae918 | 9 (8/8 hand-verifiable sample passed) | 0.97 | under a minute | @uae918 (7–2) |
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. 1,617 of the 1,617 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,277 comparable posts for this entry, running 8 August 2026 to 13 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 8 channels, the one whose matching posts we hold earliest is @hyxw3. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 14 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 8 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 |
|---|---|---|
| 12 Nov 2026, 09:47 | 76,379 | +648 |
| 10 Nov 2026, 10:04 | 75,731 | -366 |
| 8 Nov 2026, 18:31 | 76,097 | -1,405 |
| 7 Nov 2026, 08:24 | 77,502 | -219 |
| 6 Nov 2026, 11:39 | 77,721 | +720 |
| 5 Nov 2026, 09:27 | 77,001 | -166 |
| 4 Nov 2026, 05:49 | 77,167 | -177 |
| 3 Nov 2026, 07:48 | 77,344 | -214 |
| 2 Nov 2026, 06:50 | 77,558 | -77 |
| 1 Nov 2026, 03:15 | 77,635 | -278 |
| 31 Oct 2026, 00:29 | 77,913 | -434 |
| 30 Oct 2026, 02:10 | 78,347 | -1,180 |
| 29 Oct 2026, 00:48 | 79,527 | -403 |
| 28 Oct 2026, 00:37 | 79,930 | -45 |
| 27 Oct 2026, 03:10 | 79,975 | -164 |
| 26 Oct 2026, 01:51 | 80,139 | -88 |
| 25 Oct 2026, 05:10 | 80,227 | -140 |
| 24 Oct 2026, 08:14 | 80,367 | -408 |
| 23 Oct 2026, 11:05 | 80,775 | -130 |
| 22 Oct 2026, 12:37 | 80,905 | first reading |
2,605 posts held, back to 8 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 195 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 1 of 776 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 2,605 (8 August 2026 – 14 November 2026) |
| Views total | 672,456 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 07:32 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 14 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 304 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.
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 2 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 1 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 5 October 2026 to 14 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 776 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).
#群友投稿：小时候总以为公主都在城堡里，长大了才知道，公主都在包厢里，陪伴公主的也不是王子，而是王总。 她说她喜欢海，原来是王总的地中海；她说她喜欢小动物，原来是王总的宝马和路虎；她说她想要个家，后来我才知道，那是巴黎世家。算命先生说她命里有一劫，原来是王总送的保时捷。 20岁的她风华正茂，而20岁的我却穷困潦倒。她说她不喜欢钱，但感动她的每个瞬间都需要钱。后来我明白了，高冷女神并不是不爱笑，而是你的资产撑不起爱笑的她。 有些女孩并不是追来的，而是从一开始就已经确定了。或许大部分男生都注定留不住自己的白月光吧。你让她陪王子长大，她不如陪王总说说心里话。 兄弟们，努力敲键盘吧！女孩们不会一直风华正茂，我们也不会一直穷困潦倒。长江后浪推前浪，等你从一事无成的小伙变成王总时，你的温床和副驾，也会拥有别人心中的白月光。 🔔华人头条：@FFFFG ✅投稿爆料：@feihang
#群友投稿：这个故事很长，得慢慢说。我是来找一个女性朋友，有点胖，备注是“小田”。 2022年5月份偷渡出来。当时我一个人去到广东，在恩平集合，总共来了两个人，一个瘦瘦高高的，一个是女孩子，她告诉我们叫小田。当时说她是打官司保出来的，不想在家等死，然后从甘肃那边打车一路坐到广东。 当时我们三人就在一起等通知出发，等了好多天，我自己都忘了。当时让去阳江出发，那里应该是一个当地的旅游地方，我也忘了叫什么了。去了一个民宿里面，一个房间待了七八个人。 那时候没想太多，就等着晚上。有人不想去，门又出不去，结果给报警了。然后警察来了，楼上跑了几个。当时我也想着应该没事，让下楼去。人都懵逼了，一百多号人，结果全部送去旁边的派出所，然后分批关押。这一关就是38天。 出来了，我们也在联系。当天出来，我们这边联系人没安排钱，我这边给家里朋友喊转了点，够凌晨酒店三个人开房。当时在出来的阳江公安局门口喝酒喝到早上，回去睡觉。 过了几天，后面应…
#泰国资讯：芭堤雅抓获台湾籍通缉犯，身负15项通缉涉谋杀、洗钱及诈骗7000万泰铢 11月13日报道，泰国警方近日在春武里府芭堤雅展开抓捕行动，成功逮捕一名50岁台湾籍男子 Teng Chi Chen。该男子在台湾身负15项通缉，涉及1起谋杀案、1起洗钱案以及13起诈骗案，涉嫌诈骗金额超过7000万泰铢。 据报道，嫌疑人此前逃往泰国，并将旅游签证转换为退休签证，长期在当地居留。期间，他还与两名泰国合伙人共同成立一家珠宝公司，并担任公司董事。 根据台湾方面提供的线索，驻泰台北经济文化办事处向泰国旅游警察通报相关情况。泰国警方随后锁定嫌疑人藏匿于春武里府芭堤雅邦拉蒙县农普鲁地区。 当地移民局先行撤销其签证，并联合旅游警察展开抓捕部署。11月12日下午5时许，嫌疑人走出住所时被警方当场逮捕。 警方目前正在调查其名下珠宝公司的银行账户及资金往来，排查是否存在利用公司转移犯罪所得的情况。不过，截至目前，尚未发现该公司与台湾方面的…
5名中国人涉嫌 #制造假钞 #缅甸 佤邦抓获后，已移交中国警方 11月13日消息，#缅甸佤邦 司法部门通报，5名中国籍人员因涉嫌参与制造假钞被成功抓获。11月12日，佤邦方面已通过云南孟连县勐阿边境口岸，将5人正式移交中国警方。 此次行动是应中国警方跨境协查请求展开的。中方此前向佤邦提供嫌疑人线索，双方联合追查后将5人全部抓获。目前，案件已移交中方，后续将依法调查处理。 🔔华人头条：@FFFFG ✅投稿爆料：@feihang
#厕所 #打飞机 太饥渴了 🔔华人头条：@FFFFG ✅投稿爆料：@feihang
#网友爆料：中国资金盘APP：“大国崛起”，三方聊天APP：协同互联，主管：香蕉（又名候天来）总监：阿杰（又名杰少） 原公司地址：柬埔寨西港海悦大酒店801办公室。后因被曝光，不得已搬迁至格鲁吉亚巴统市。 答应员工保证办理工作签证！员工跟随公司入境格鲁吉亚后，却告知员工护照要逾期黑着。 辛辛苦苦跟随公司半年，最后不得已被迫离职，还被拉赔付1300美金。前期曝光了一些聊天记录，后续公司补发我7000美金工资，提成我都没要！我做到仁至义尽！ 原本以为出来东南亚都是为了求财，大家都不容易，好聚好散！我原本不想撕破脸皮，拽上无辜的同事！只是香蕉，我没想到你做人做事太不讲究！ 事情处理结束后，拿曝料我的信息资料到处抹黑我，整个办公室的人都有我个人资料！说我敲诈公司7万美金！满嘴跑火车，侮辱我，说我是代理，是公司骨干，说我倒卖人口去黑园区！给我家里人寄茶叶，找人实名举报我，用这些下三滥的手段来威胁我！ 不做亏心事，不怕鬼敲门！ …
回国三个月了，在柬埔寨经历了很多。东南亚的路，注定不是一帆风顺。 从懵懂无知到饱经世故，或许成长是伴随着痛苦、压力、绝望、排挤和冷眼的。我依然觉得，这是一件好事情，能够打磨自己的心气，磨练自己的抗压能力。 这两年最可惜的是，自己没有带着钱回来。或许是自己时运不济，或许是自己还不够努力。从一个职场小白，学会了怎么去讨好领导，维护同事之间的关系。从西港到七星海，再到金边，一路走到现在。 也后悔当初自己跟自己较劲。如果当时把较劲的注意力放到客户上、事业上，或许我现在的结果会是另一种吧。 感觉柬埔寨的经历就像一场梦。回国之后，开始后悔自己回来的选择。我和曾经国内玩伴的生活开始脱轨，不管是兴趣还是认知，都有了不同。在国内也很无聊，没事就看看飞机。 随后，看到东南亚大事件里面的曝光接二连三地出，我就知道，东南亚这条路已经开始模糊了。 唉，十分感谢这段经历对我的千锤百炼。很感谢之前的公司，我就不提集团了。相遇皆是缘分。 最后一句…
#国内资讯：庆阳打掉裸聊敲诈团伙抓获17人 警方提醒勿因羞耻沉默！ 甘肃庆阳警方近日打掉一个裸聊敲诈团伙，17名犯罪嫌疑人被抓。该骗局以广告引流、录播视频诱导裸聊、木马窃取通讯录和隐私影像为链条，最后以"发给亲朋好友"相威胁索要钱财。 许多人第一反应是花钱消灾，但转账只会让对方视你为"还能继续榨"的对象，越给越多。屏幕那头的"艳遇"往往只是流水线剧本，真正值钱的筹码是手机里的通讯录和面子。 🔔华人头条：@FFFFG ✅投稿爆料：@feihang
#网友曝光 我之前被代理阿欲带去了七星海，进了所谓的“江总团队”。当时阿欲在电话里说得特别好听，包吃包住，代理费可以预支，做满三个月还有提成。结果刚进去第一天，护照就被公司收走了，说是统一拿去办签证。直到现在，护照没还给我，工资也一分钱没拿到。 刚去的第一个月，公司根本不让我们正常上班，天天逼着我们拉人，要求把身边的朋友、同学都叫过来，说拉到人才算业绩。我当时也是傻，连自己的发小阿峰都叫来了。 等人招得差不多了，公司才开始安排我们上班。每天一干就是十五六个小时，提成方案还改来改去，越改越少。业绩不达标就罚站、扣钱，松哥甚至还会动手打人，公司也没人管。 阿欲后来也没落到什么好下场。他前前后后垫了三万多代理费，去找江总要钱，江总还笑着跟他说：“都是自家兄弟，下个月一起结。”结果到了下个月，阿欲就被调去了别的组，之后再也没见过他。后来我才听说，当时那批十几个人，竟然被江总整批卖去了其他园区。 今年风声越来越紧，缅甸那边的园区被…
缅甸木姐郊外南翁村一处名为雅泰农场诈骗窝点有20人从该区域逃脱，目前由三兄弟联盟控制的武装力量窝点。 11月8日，20多名在诈骗窝点工作的人员从“雅泰农场”逃出，进入了南翁村及其周边地区。其中还包括一名据说是俄罗斯籍的男子。 当同盟军进行追捕时，部分人被重新抓获并被同盟军士兵带走”据当地人反映，虽然部分逃出者被同盟军武装（MNDAA）成员抓回，但具体被带走的人数尚不清楚。 据当地居民介绍，这些从事“网络诈骗”活动的人员所逃离的雅泰农场，位于南翁村外。在“1027行动”之前，该地点由“龙堂（龙潭）民团占据。 另一位当地居民解释说，在“1027行动”期间，随着德昂民族解放军（TNLA）攻占了相关城镇，龙堂（龙潭）民团撤离了该处。 此后，该地点先是被TNLA武装力量占据，随后又被果敢民族民主同盟军（MNDAA）接管；目前，该处由MNDAA人员控制。 “那个‘雅泰农场以前是个草莓园，过去‘龙堂（龙潭）民团曾驻扎在那里，但现…
#网友曝光：四川卢显峰长期盘踞在柬埔寨波贝做诈骗因上班期间飞单被管理查到被打然后赔钱回国，现又通过广东的余增强介绍一起到巴西转到巴拉圭盘口继续搞诈骗.. 广东的余增强长期盘踞在老挝万象城，因上班期间飞单被主管查获被打赔钱赶出公司，从老挝飞到巴西再转到巴拉圭盘口做诈骗。 他们两个在公司是顶尖的操盘手业绩很好，长期都是做中国盘，都是骗同胞的钱..缺德的两个垃圾，赚到钱就赌和嫖，还骗很多老乡出去上班，我就是其中一个，把我们骗到柬埔寨后公司给了他代理线，业绩不好他就怂恿管理要给我们教训天天体罚，最后我还花了2万U才让我回国。 卢显峰和余增强两个是好兄弟，什么资源都是共享的，都是用各种方法骗国内老乡出国给他们凑代理人数，曝光他们两个不为什么就希望通过贵平台让更多人知道这两个败类……避免更多人上当受骗，在巴拉圭接收他们的盘口老板要经常查他们的客户，他们两个是出了名的飞单侠。 🔔华人头条：@FFFFG ✅投稿爆料：@feihang
#网友投稿：有时候我会想，自己是从什么时候开始对键盘产生这种奇妙的依赖感的。 刚进公司的时候，对键盘其实是陌生的，敲字只是工作的一部分，是完成任务的工具。 可这几年下来，我在一段段和客户的对话中，一次次敲击键盘，慢慢地开始感受到那种节奏与表达带来的微妙变化。 每一个字从指尖落下，都像是有温度的、有情绪的，不再只是冷冰冰的符号，而是承载着沟通、理解，甚至一点点情感的延伸。 渐渐地，我发现自己开始享受这种感觉，甚至不再满足于普通的办公键盘，会去在意手感、声音、反馈。当我坐在工位上，没有客户聊天的时候，手指竟会不自觉地发痒，仿佛在等待下一次敲击的开始。 🔔华人头条：@FFFFG ✅投稿爆料：@feihang
Showing the 12 most recent of 2,605 posts we hold for @hyxw6. 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 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.
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 13 seed channels' Telegram-generated recommendation lists 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“迪拜新闻头条” (@hyxw6), 76,379 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/hyxw6.
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.