Channel
@dibaiTT
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
153,378subscribers
-8,567 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001892746324 |
|---|---|
| Type | Channel |
| Username | @dibaiTT |
| Description | 联系： @annibaobei520 甩人 @dibaiSB 新闻 @dibaiTT 二手 @dibai246 吃瓜 @chiguazhongxin3 修车大全 @dibaiyuepao 红楼会所 @dibaihonglou |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/dibaiTT |
National news — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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 5 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 |
|---|---|---|---|
| @taiguopindao/3855013 Aug 2026, 14:49 UTC | @dibaiTT/50859 · this entry13 Aug 2026, 14:49 UTC | 1.00 | under a minute |
| @dibaiTT/51725 · this entry27 Aug 2026, 09:30 UTC | @taiguopindao/3928827 Aug 2026, 09:31 UTC | 1.00 | under a minute |
| @dibaiTT/51948 · this entry30 Aug 2026, 15:37 UTC | @taiguopindao/3947530 Aug 2026, 15:37 UTC | 1.00 | under a minute |
| @taiguopindao/4023615 Sept 2026, 14:29 UTC | @dibaiTT/52933 · this entry15 Sept 2026, 14:29 UTC | 1.00 | under a minute |
| @taiguopindao/409122 Oct 2026, 06:29 UTC | @dibaiTT/53833 · this entry2 Oct 2026, 06:30 UTC | 1.00 | under a minute |
| @taiguopindao/4140212 Oct 2026, 07:23 UTC | @dibaiTT/54312 · this entry12 Oct 2026, 07:23 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @taiguopindao | 1,096 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @taiguopindao (1,011–85) |
| @dongnanyadashijian9 | 493 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @dongnanyadashijian9 (423–70) |
| @sililanka007 | 444 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @sililanka007 (383–61) |
| @jianpuzhai_01 | 368 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @jianpuzhai_01 (310–58) |
| @dubaixinwen2 | 52 (5/8 hand-verifiable sample passed) | 0.96 | 2 days | this entry (52–0) |
| @dibai8 | 39 (5/8 hand-verifiable sample passed) | 0.95 | 1.8 hours | @dibai8 (39–0) |
| @XLABdxb | 20 (8/8 hand-verifiable sample passed) | 0.94 | 2.5 hours | @XLABdxb (17–3) |
| @daxxx | 20 (5/8 hand-verifiable sample passed) | 0.92 | 1.9 hours | @daxxx (18–2) |
| @bc123cobg | 12 (6/8 hand-verifiable sample passed) | 0.99 | 2 days | this entry (12–0) |
| @RR8vip | 10 (7/8 hand-verifiable sample passed) | 1.00 | 2 days | this entry (10–0) |
| @dubai0 | 9 (8/8 hand-verifiable sample passed) | 0.89 | 61 minutes | @dubai0 (9–0) |
| @woaidibai | 9 (6/8 hand-verifiable sample passed) | 0.97 | 9.8 hours | this entry (9–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. 2,219 of the 2,219 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,100 comparable posts for this entry, running 7 August 2026 to 10 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 5 channels, the one whose matching posts we hold earliest is @dongnanyadashijian9. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 11 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 5 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 |
|---|---|---|
| 10 Nov 2026, 20:35 | 153,378 | -2,334 |
| 9 Nov 2026, 07:21 | 155,712 | -2,061 |
| 7 Nov 2026, 21:59 | 157,773 | -1,980 |
| 6 Nov 2026, 19:18 | 159,753 | -1,218 |
| 5 Nov 2026, 18:07 | 160,971 | -959 |
| 4 Nov 2026, 19:10 | 161,930 | -1,248 |
| 3 Nov 2026, 18:18 | 163,178 | -363 |
| 2 Nov 2026, 21:06 | 163,541 | -262 |
| 1 Nov 2026, 23:09 | 163,803 | -2,072 |
| 1 Nov 2026, 00:20 | 165,875 | -1,748 |
| 30 Oct 2026, 22:29 | 167,623 | -2,810 |
| 30 Oct 2026, 00:55 | 170,433 | -2,295 |
| 28 Oct 2026, 22:15 | 172,728 | -2,877 |
| 27 Oct 2026, 23:27 | 175,605 | -1,694 |
| 26 Oct 2026, 23:50 | 177,299 | -3,025 |
| 25 Oct 2026, 20:26 | 180,324 | +17,928 |
| 24 Oct 2026, 20:27 | 162,396 | +8,427 |
| 23 Oct 2026, 21:36 | 153,969 | -1,504 |
| 22 Oct 2026, 21:05 | 155,473 | -3,157 |
| 21 Oct 2026, 15:57 | 158,630 | first reading |
2,386 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 194 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 292 of 714 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 2,386 (7 August 2026 – 10 November 2026) |
| Views total | 610,351 |
| Reactions total | 322 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 03:18 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 11 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 238 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.
574 reactions across 494 posts, in 12 distinct kinds. The most used accounts for 23.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 132 | 23.0% | |
| ❤ | 81 | 14.1% | |
| 👏 | 64 | 11.1% | |
| 🔥 | 56 | 9.76% | |
| 😁 | 56 | 9.76% | |
| ⚡ | 47 | 8.19% | |
| 🤩 | 47 | 8.19% | |
| 🎉 | 46 | 8.01% | |
| 🥰 | 42 | 7.32% | |
| 🙏 | 1 | 0.174% | |
| 🤔 | 1 | 0.174% | |
| 🤣 | 1 | 0.174% |
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 498 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 574 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 2 October 2026 to 10 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 743 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亿迪拉姆，3公里，两个车站：迪拜地铁要在2031年延伸至阿勒马克图姆国际机场 20亿迪拉姆，3公里，两个车站，2031年通车。迪拜地铁要向正在建设中的阿勒马克图姆国际机场城（Al Maktoum International Airport City）再伸出一段。 11月10日，迪拜王储谢赫·哈姆丹·本·穆罕默德·本·拉希德·阿勒马克图姆在迪拜执行委员会会议上批准了这一延伸项目。这段3公里的延长线将从现有的“2020年路线”（Route 2020）延伸出去，新建两个车站，直接把地铁接到机场西航站楼。项目由迪拜道路与交通管理局（RTA）及迪拜工程项目管理局（Dubai Engineering Projects Establishment）负责实施。 延伸线通车后，西航站楼将不再只是一个航站楼。它将与机场快线以及阿提哈德铁路（Etihad Rail）的高速铁路网实现对接，把地铁、机场铁路和城际高速铁路串到一起。对乘客、机场工…
阿布扎比国家石油公司确认一艘船只在阿联酋领海遭袭受损 当地时间10日晚，阿联酋阿布扎比国家石油公司发布声明称，当天下午该公司一艘船只在波斯湾阿联酋领海遭袭受损。 👻😇🥰😘🔥🔥🔥🔥🔥💩✍️🍡🎈 ✅👩💻我要投稿 😘安妮宝贝： ——————————————————— 😳求职招聘 📑迪拜新闻 ✴️二手市场 🍉吃瓜中心 💻搭建开发
继续友情提醒下：iOS 又有安全更新了…iPhone 已经不如以往那样的“安全”，各种恶意利用在冒出… 不乱安装 App，不乱打开陌生网页（尤其涉黄的… 以前这种提醒主要都是针对 Windows 的，时代变了
阿联酋人怎么看待“双11光棍节”？明知是营销噱头，但仍忍不住“剁手” “如果喜欢，就该把它放进购物车！” 碧昂丝这句话，在“双11”临近的时候，被很多人认真执行了。这一天不像情人节，你不需要为谁准备礼物——你只需要好好犒劳自己。与其叫它“光棍节”，不如叫它“悦己日”。 这个“节日”最早起源于中国，最初带着“反情人节”的意味，让没有伴侣的人有一个属于自己的节日。后来商业力量加入进来，它逐渐变成一场全球性的购物狂欢，规模甚至超过了“黑色星期五”。在阿联酋，它的打开方式也差不多：11月11日，打开购物应用，把心仪的东西加进购物车，挑一挑，然后下单。这一天属于所有人——单身也好，已婚也好，主题只有一个：为自己花点钱。 在阿联酋，“双11”怎么玩 在阿联酋，“双11”主要是一场线上促销。Noon和亚马逊（Amazon）等平台已经全面开启大促，折扣最高到90%，部分商品低至1迪拉姆（Dh1），配送时效从15分钟到当日送达不等。 v…
以色列：迪拜航空航班遇袭事件乘客为敌对事件受害者 当地时间11月9日，以色列国防部宣布，正式将9月30日乘坐迪拜航空FZ1073航班的以色列乘客认定为敌对事件受害者。 目前，该决定已提交至以色列国家安全局（辛贝特）进行后续处理。 👻😇🥰😘🔥🔥🔥🔥🔥💩✍️🍡🎈 ✅👩💻我要投稿 😘安妮宝贝： ——————————————————— 😳求职招聘 📑迪拜新闻 ✴️二手市场 🍉吃瓜中心 💻搭建开发
月收入5万也能申请结婚补助了——沙迦酋长在一档广播节目里做了这个决定 沙迦酋长谢赫·苏尔坦·本·穆罕默德·阿勒卡西米下令，将结婚补助金的薪资资格上限从原来的3万迪拉姆提高到5万迪拉姆。这意味着，月收入在5万迪拉姆及以下的个人，现在也能申请这项由统治者办公厅提供的补助。消息是他在沙迦广播电视局的“直接连线”节目中，回应一位听众的请求时宣布的。 从3万到5万，覆盖面的扩大是直接的。原本够不着门槛的那部分人，被纳进了补助范围。 👻😇🥰😘🔥🔥🔥🔥🔥💩✍️🍡🎈 ✅👩💻我要投稿 😘安妮宝贝： ——————————————————— 😳求职招聘 📑迪拜新闻 ✴️二手市场 🍉吃瓜中心 💻搭建开发
45天，第32届迪拜购物节回来了：开幕周末，海湾变成了一块屏幕 第32届迪拜购物节（DSF）在这一天正式回归，一直持续到2027年1月17日，整整45天，是这项活动有史以来最长的一届。规模更大、形式更大胆、互动性更强——官方是这么形容的，而开幕周末的安排，也确实撑得起这句话。 👻😇🥰😘🔥🔥🔥🔥🔥💩✍️🍡🎈 ✅👩💻我要投稿 😘安妮宝贝： ——————————————————— 😳求职招聘 📑迪拜新闻 ✴️二手市场 🍉吃瓜中心 💻搭建开发
黑客也太与时俱进了，iOS 27 都已经是现在这代正式系统了，这漏洞 worse_query 直接打到 27.2，恶意 App 能跨沙盒去读别的应用本地文件，助记词、私钥要是明文放在手机里，就有被掏走的风险。
黄果短剧都开源了？？！？ 还得是GitHub……
Pavel Durov 表示，48 小时内在 Telegram 上创建了超过 70 万个自托管钱包。
#币圈资讯 特朗普旗下公司最新披露，目前持有15,649枚比特币，总价值约11.7亿美元。 今年第三季度，该公司又增持了1,510枚比特币，价值约1.13亿美元。 当市场上的人都在恐慌时，特朗普却在持续加仓，为下一轮加密货币牛市做准备。 👻😇🥰😘🔥🔥🔥🔥🔥💩✍️🍡🎈 ✅👩💻我要投稿 😘安妮宝贝： ——————————————————— 😳求职招聘 📑迪拜新闻 ✴️二手市场 🍉吃瓜中心 💻搭建开发
#南洋半生 如履薄冰半世行， 偏踏南洋万里程。 少时不懂人间苦， 半生漂泊异国城。 曾怀壮志闯南洋， 如今狗推话沧桑。 白日键盘敲梦想， 夜深孤枕伴愁肠。 一身疲惫无人问， 满嘴牛皮自己扛。 昨日还谈赚千万， 今朝又在找下家。 西装穿过几回旧， 业绩吹过几多场。 朋友圈里风光无限， 银行卡里略显凄凉。 缅甸风雨柬埔寨， 泰国越南又一场。 南洋走过千重路， 回头已是半生霜。 少年不知归家路， 中年方晓故乡长。 父母盼儿门前坐， 儿在异乡数月光。 若问此生何所获， 一身故事半身伤。 南洋已过半生路， 梦里依旧是故乡。 👻😇🥰😘🔥🔥🔥🔥🔥💩✍️🍡🎈 ✅👩💻我要投稿 😘安妮宝贝： ——————————————————— 😳求职招聘 📑迪拜新闻 ✴️二手市场 🍉吃瓜中心 💻搭建开发
Showing the 12 most recent of 2,386 posts we hold for @dibaiTT. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
@dibaiTT named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 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 40 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“🌏迪拜新闻曝光-安危头条🇦🇪迪拜通🔥” (@dibaiTT), 153,378 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/dibaiTT.
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.