Telegram RegisterThe public register of Telegram
Telegram profile photo for 迪拜新闻|迪拜大事件|东南亚大事件

Channel

迪拜新闻|迪拜大事件|东南亚大事件

@dibaif

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

13,536subscribers

-140 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002111667832
TypeChannel
Username@dibaif
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/dibaif

Topic

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 39% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear word for word on 3 other registered channels. They sit inside a group of 9 channels that share the same post bodies 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@miandianQ/580226 Aug 2026, 14:01 UTC@dibaif/72047 · this entry7 Aug 2026, 14:01 UTC1.0024 hours
@miandianQ/580236 Aug 2026, 14:05 UTC@dibaif/72048 · this entry7 Aug 2026, 14:05 UTC1.0024 hours
@miandianQ/580256 Aug 2026, 14:58 UTC@dibaif/72060 · this entry7 Aug 2026, 14:59 UTC1.0024 hours
@miandianQ/581767 Aug 2026, 14:13 UTC@dibaif/72049 · this entry7 Aug 2026, 14:16 UTC1.002 minutes
@miandianQ/581827 Aug 2026, 14:27 UTC@dibaif/72055 · this entry7 Aug 2026, 14:28 UTC1.00under a minute
@miandianQ/581857 Aug 2026, 14:30 UTC@dibaif/72058 · this entry7 Aug 2026, 14:31 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@miandianQ11 (8/8 hand-verifiable sample passed)1.0072 seconds@miandianQ (11–0)
@yuenanU10 (8/8 hand-verifiable sample passed)1.00under a minute@yuenanU (10–0)
@baoliaoc8 (8/8 hand-verifiable sample passed)1.00under a minute@baoliaoc (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. 29 of the 29 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 23 comparable posts for this entry, running 7 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 9, the earliest publisher we hold is @miandianQ. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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.

Also posting the same content

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.

Growth

13,53613,67613,6067 August 2026 — 13,676 subscribers7 August 2026 — 13,676 subscribers9 August 2026 — 13,674 subscribers10 August 2026 — 13,671 subscribers11 August 2026 — 13,668 subscribers11 August 2026 — 13,660 subscribers13 August 2026 — 13,651 subscribers14 August 2026 — 13,649 subscribers16 August 2026 — 13,646 subscribers17 August 2026 — 13,636 subscribers18 August 2026 — 13,633 subscribers19 August 2026 — 13,631 subscribers20 August 2026 — 13,630 subscribers21 August 2026 — 13,626 subscribers23 August 2026 — 13,620 subscribers24 August 2026 — 13,611 subscribers26 August 2026 — 13,602 subscribers28 August 2026 — 13,603 subscribers29 August 2026 — 13,597 subscribers30 August 2026 — 13,596 subscribers31 August 2026 — 13,589 subscribers1 September 2026 — 13,585 subscribers2 September 2026 — 13,581 subscribers4 September 2026 — 13,578 subscribers7 September 2026 — 13,566 subscribers10 September 2026 — 13,558 subscribers12 September 2026 — 13,553 subscribers14 September 2026 — 13,547 subscribers15 September 2026 — 13,542 subscribers17 September 2026 — 13,536 subscribers7 August 202617 September 2026
30 measurements spanning 41 days, net -140. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 13,515–13,697 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
17 Sept 2026, 19:0013,536-6
15 Sept 2026, 19:5613,542-5
14 Sept 2026, 05:3813,547-6
12 Sept 2026, 12:1713,553-5
10 Sept 2026, 08:2113,558-8
7 Sept 2026, 04:5913,566-12
4 Sept 2026, 13:1913,578-3
2 Sept 2026, 21:1513,581-4
1 Sept 2026, 16:3313,585-4
31 Aug 2026, 17:2513,589-7
30 Aug 2026, 19:5313,596-1
29 Aug 2026, 19:1313,597-6
28 Aug 2026, 17:2613,603+1
26 Aug 2026, 19:5813,602-9
24 Aug 2026, 20:5313,611-9
23 Aug 2026, 04:3513,620-6
21 Aug 2026, 20:1613,626-4
20 Aug 2026, 14:1413,630-1
19 Aug 2026, 13:0813,631-2
18 Aug 2026, 16:0813,633first reading

Engagement

587 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 49 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.052%
avg views ÷ 13,536 subscribers
Avg views / post
7.1
138 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
138
of 587 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held587 (7 August 2026 – 2 September 2026)
Views total976
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 19:59 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.

What this channel posts

Video runtime
2h 09m
Average length
31s

Measured directly from 251 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.

Reaction mix

5 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤480.0%
🔥120.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 6 of the 587 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 587 most recent posts we hold, published 7 August 2026 to 2 September 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.

Recent posts

2 Sept 2026, 19:14 UTC3 viewsread 2 September 2026
Photo

#温馨提示:最近柬埔寨开启新一轮的大检查,有护照的尽量别住小酒店和小公寓,最好去一些大酒店和公寓住,这样即使被检查也不会被打野的连累到。 很多住小酒店和公寓的虽然没有任何违法行为,但不能保证因为那些打野团队的影响被带走,还有就是房间别放任何电脑,玩游戏的也不行。 今天西港检查,部分证件齐全、居住在小公寓、小型酒店的人员,因与“打野”涉诈人员住在同一处,遭到连带,一同被警方带走调查。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888

2 Sept 2026, 18:32 UTC6 viewsread 2 September 2026
Photo

#网友投稿:金三角特区“孟赛物业”当地时间11点多的时候被治安局突击包围了,抓了一伙打野的团队。 截至目前,行动仍未结束,大楼前后门均还是封锁状态,治安局的车正在拉办公设备! 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888

2 Sept 2026, 18:12 UTC7 viewsread 2 September 2026
Video

迪拜警察总部发布视频,展示新学年开学期间对迪拜多所学校的走访活动,包括迪拜中国学校,与学生互动以建立联系。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888

2 Sept 2026, 18:04 UTC8 viewsread 2 September 2026
Photo

6人借旅游出境!辗转柬埔寨西港金贝、老挝金三角多园区、缅甸妙瓦底老泰昌园区从事电诈获刑 贵州黔南政法机关9月1日对外通报: 近日,由平塘县人民检察院提起公诉的一起诈骗罪、偷越国(边)境罪一审宣判,六名被告人全部被判处刑罚。 经查,被告人刘某某受陆某(未到案)邀约,以个人旅游为借口办理护照出境。刘某某出境后,又邀约王某某、敖某某出境;王某某接受邀约后,继续邀约秦某某出境;刘某某还通过韦某城(未到案),由韦某城邀约韦某彤、杨某某出境。 上述六名被告人均以个人旅游为借口办理护照,自2023年4月起先后出境,期间辗转柬埔寨西港金贝园区诈骗公司、老挝金三角特区天海诈骗公司等多个诈骗窝点从事电信网络诈骗活动。 六名被告人陆续进入老挝金三角特区天海诈骗公司后,一起在天海诈骗公司所在的“老缅新村”诈骗园区、“金帝诈骗园区”实施诈骗至2024年2月,之后六名被告人一同前往缅甸妙瓦底“老泰昌”诈骗园区,以虚拟币投资理财的方式实施电信诈骗。 …

2 Sept 2026, 17:51 UTC8 viewsread 2 September 2026
Photo

#群友吐槽:为什么很多扶手女觉得自己怀孕了,然后找金主要300万人民币买个生活保障,这事很正常? 我作为东南亚拥有8年之久的观察员身份,说出这些“扶手”对这个所谓的生活保障要300万,大致内心想法方向,去说一个事实: 你无非就是以怀孕的名义去赚到一笔比你以往做(扶手、全球空降兵)更高的报酬罢了。以怀孕的名义去争取300万的天价生活保障费,真当自己的逼长金了? 我们来举个例子:王思聪前女友黄一鸣为王思聪生下一女,而王家才对外公开说,因为孩子的原因,每个月才给予部分的抚养费。而你作为一个扶手,现在也只是怀个孕而已,你张口就是要300万。 往远的说,你无非就是想赚到这一笔,然后直接退圈。往近的说,你无非就是想赚到这笔钱,然后把小孩打了,之后潇洒个一年半载,先满足自己的那个虚荣心,然后重操旧业罢了。 真当自己是人上人了,还要300万?你怎么不学景甜,要孙宇晨5000万呢?给你三五十万就很不错了,打胎才几个钱?别蹬鼻子上脸,怀个…

2 Sept 2026, 17:43 UTC7 viewsread 2 September 2026
Photo

莫迪劝全体印度人:别买黄金!别去国外旅游!别去海外结婚 “如果没必要,就不要买黄金。如果出国是为了旅游,就不要去了。如果要去海外结婚,也不要这么做。” 9月1日,印度总理莫迪在社交媒体上发布视频,给全体印度人提了三条建议。 莫迪给出的建议十分具体。 第一,非必要不买黄金。第二,不为了休闲而出国旅游。第三,不在海外办婚礼。他呼吁民众选择国内旅游和国内婚礼,践行“Wed in India”(在印度结婚)。 他还将这些建议与“自强精神”挂钩,“如果我们继续强调自力更生,我坚信,到2047年印度迎来独立100周年之际,我们将把一个发达的印度交给青年一代。” 这不是莫迪第一次发出如此呼吁。 今年5月,他呼吁民众避免购买黄金、推迟非必要海外旅行,还建议节约汽油柴油、减少食用油消费。 一个逻辑 莫迪的三条建议其实只遵循一个逻辑:减少外汇流出。 印度是全球第二大黄金消费国,但黄金需求严重依赖进口,黄金进口也一直是印度仅次于原油的…

2 Sept 2026, 17:31 UTC5 viewsread 2 September 2026
Photo

迪拜—沙迦交通|新Al Taawun隧道预计将等待时间最多缩短85% 随着Al Taawun隧道项目第一阶段开放,往返沙迦和迪拜的驾车者预计将迎来更短的等待时间以及更加顺畅的交通,该项目预计可将等待时间最多减少85%。 项目核心是在Al Taawun环岛下方建设一条500米长的地下隧道,旨在建立一条更加直接的路线,连接Al Taawun Street、Al Nahda Bridge和迪拜。 第一阶段包括隧道本身,以及通往Sheikh Mohammed bin Zayed Street和Emirates Road的连接道路,预计于2026年11月开放,赶在下一届沙迦国际书展之前投入使用。 整个项目计划于2027年2月完工。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888

2 Sept 2026, 17:09 UTC7 viewsread 2 September 2026
Video

#网友投稿:缅甸亚太四号地路口在查车,现在这帮狗逼又要出来捞钱了,不想给钱就直接干深蹲200下。 PS:不是抓去警局,还比较人性化🤣 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888

2 Sept 2026, 16:48 UTC7 viewsread 2 September 2026
Photo

在泰国芭提雅你可能会看到这些袖子上带有SLG的人在本周在芭提雅四处走动 他们是岸上巡逻队,到处活动,确保数千名美国水手和海军陆战队员的安全, 帮助解决任何问题,并确保遵守规章制度,比如某些区域禁止进入。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @Bnnc888

2 Sept 2026, 15:52 UTC13 viewsread 2 September 2026
Photo

8名印尼人被指遭到欺骗,被招募成为俄罗斯士兵 据乌克兰情报部门向印度尼西亚政府分享的情报,8名印尼公民被招募前往俄罗斯当兵,而据称他们是以受骗的方式被招募的。CNA于2026年9月2日(星期三)报道了这一消息。 乌克兰对外情报局(FISU)表示,这些印尼人据称是被“高薪工作”的承诺骗过去的,但之后却被招募加入俄罗斯军队。 FISU于8月27日在其官网表示: “俄罗斯仍在持续、有组织地招募外国人,让他们参与对乌克兰的战争,而印度尼西亚就是这一趋势的最新例子。” 不过,FISU并没有明确说明这些印尼人是否已经被派往乌克兰参战。 印度尼西亚国会副议长 苏夫米·达斯科·艾哈迈德(Sufmi Dasco Ahmad)9月1日(星期二)证实,乌克兰方面确实已经将这项情报分享给印尼政府。 他表示,印度尼西亚情报部门和外交部正在协调处理这一问题。 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @…

2 Sept 2026, 15:50 UTC12 viewsread 2 September 2026
Photo

不要和陌生人说话:网友讲述自己在金边遭遇绑架的真实经历。 网友投稿:在柬埔寨待了有快4年,自认为也算是富有生活经验的一名老狗推,但是后来想想,其实大部分时间在园区渡过,哪有什么经验。 某天晚上,我在金边一家本地酒吧喝酒,我是一个人去的。坐了一会儿以后,有个男的过来跟我聊天,他也是中国人,就问我来柬埔寨多久了,做什么的,住在哪里这些。我当时觉得也没什么(毕竟这边大家都是一些虚假信息和身份,无关紧要),再说也就是聊天还能怎么样。 后来他还说自己在这边做生意,认识很多人,怎么怎么的,也是因为现在的局势不好,天天一个人在金边,喝点小酒。再后来就要和我加个联系方式,出于礼貌,也不好意思拒绝,就加了一个。 过了几天,他又找我,说晚上一起喝酒。我本来是不太想去的,也不太敢去,但是他说还是上次那个酒吧,这我听了就感觉也没什么,我就去了。 这次聊的就多了,有没有女朋友,在这边有没有什么朋友,什么时候回国,我当时也都说了,半真半假。 就…

2 Sept 2026, 15:29 UTC10 viewsread 2 September 2026
Photo

新全迅网 · 娱乐平台风向标 💎查信誉 · 看曝光 · 找优惠 🥇新全迅网致力于打造公开、公正、透明的娱乐平台信息服务体系,依托全网数据监测、真实用户反馈及多维度数据分析,为广大用户提供平台信誉查询、风险预警、黑平台曝光、优惠信息整合等一站式服务。 🥈我们坚持以真实评价为依据,以数据分析为支撑,持续完善平台信誉评级与风险预警机制,让每一位用户都能获得更加真实、可靠的参考信息。 🥉同时,汇聚全网真实优惠资源,精选各大平台优质福利,拒绝虚假宣传与噱头,让每一份优惠都真实可查、一目了然。 我们的使命 ✅ 选平台,先查信誉,选择更放心。 ✅ 避风险,先看曝光,远离黑平台。 ✅ 找优惠,真实精选,拒绝套路。 ✅ 查数据、看口碑、享福利,一站式解决娱乐信息需求。 新全迅网——让数据说话,让信誉可查,让每一次选择都更加安心。 ✅你了解娱乐平台信息的第一站 关注新全迅网➡️ @xqxw 收录/投稿➡️@qxwkefu

Showing the 12 most recent of 587 posts we hold for @dibaif. 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 4 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.

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.

Appears in Telegram’s recommendations for other channels

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.

东南亚大事件
@yuenanU · 219,852
Telegram ranks this channel #9 of 44 here — alongside 43 others — read 15 August 2026
东南亚
@dubai1w · 188,351
Telegram ranks this channel #9 of 45 here — alongside 44 others — read 12 August 2026
头条大事件
@alqxzs · 48,571
Telegram ranks this channel #16 of 24 here — alongside 23 others — read 28 August 2026
迪拜新闻 迪拜大事件 马来西亚大事件
@chiguak · 39,899
Telegram ranks this channel #16 of 46 here — alongside 45 others — read 23 August 2026
迪拜大事件|迪拜新闻|Dubai生活资讯攻略
@dubai0 · 77,364
Telegram ranks this channel #16 of 25 here — alongside 24 others — read 19 August 2026
🌏迪拜新闻曝光-安危头条🇦🇪迪拜通🔥
@dibaiTT · 187,895
Telegram ranks this channel #20 of 41 here — alongside 40 others — read 12 August 2026
柬埔寨大事件|新闻曝光|安危头条
@JPZDSJ · 220,328
Telegram ranks this channel #22 of 49 here — alongside 48 others — read 17 August 2026
东南亚吧 东南亚大事件
@DNYba · 122,078
Telegram ranks this channel #25 of 55 here — alongside 54 others — read 18 August 2026
西港日记|柬埔寨大事件|东南亚大事件
@xigangz · 89,934
Telegram ranks this channel #30 of 65 here — alongside 64 others — read 15 August 2026
缅甸新闻头条
@hyxw4 · 77,008
Telegram ranks this channel #40 of 55 here — alongside 54 others — read 19 August 2026

This channel appears in 10 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“迪拜新闻|迪拜大事件|东南亚大事件” (@dibaif), 13,536 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/dibaif.

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.