Telegram RegisterThe public register of Telegram
Telegram profile photo for 迪拜🇦🇪海湾大事件

Channel

迪拜🇦🇪海湾大事件

@bc123cobg

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

113,583subscribers

+80,236 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001647012236
TypeChannel
Username@bc123cobg
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/bc123cobg

Topic

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

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 in near-verbatim form on 12 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@dubaixinwen2/2540923 Aug 2026, 11:05 UTC@bc123cobg/35959 · this entry23 Aug 2026, 14:54 UTC1.003.8 hours
@dubaixinwen2/2584119 Sept 2026, 03:16 UTC@bc123cobg/36473 · this entry19 Sept 2026, 07:05 UTC1.003.8 hours
@dubaixinwen2/2621910 Oct 2026, 02:43 UTC@bc123cobg/37046 · this entry10 Oct 2026, 05:56 UTC1.003.2 hours
@dubaixinwen2/2633317 Oct 2026, 05:35 UTC@bc123cobg/37235 · this entry18 Oct 2026, 05:19 UTC1.0024 hours
@dubaixinwen2/2633417 Oct 2026, 07:04 UTC@bc123cobg/37236 · this entry18 Oct 2026, 05:20 UTC1.0022 hours
@dubaixinwen2/2637219 Oct 2026, 13:09 UTC@bc123cobg/37284 · this entry20 Oct 2026, 08:12 UTC1.0019 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@dubaixinwen2165 (7/8 hand-verifiable sample passed)1.006.3 hours@dubaixinwen2 (161–4)
@dibai866 (8/8 hand-verifiable sample passed)1.003 days@dibai8 (66–0)
@daxxx57 (5/8 hand-verifiable sample passed)1.003 days@daxxx (57–0)
@RR8vip727 (8/8 hand-verifiable sample passed)1.0072 secondsthis entry (726–1)
@woaidibai26 (8/8 hand-verifiable sample passed)0.992 days@woaidibai (26–0)
@XLABdxb22 (8/8 hand-verifiable sample passed)0.943 days@XLABdxb (22–0)
@bc123_z14 (8/8 hand-verifiable sample passed)0.91under a minuteeven
@dibaiTT12 (6/8 hand-verifiable sample passed)0.992 days@dibaiTT (12–0)
@dnymp11 (6/8 hand-verifiable sample passed)1.003 days@dnymp (11–0)
@qqxx131410 (7/8 hand-verifiable sample passed)1.002 days@qqxx1314 (10–0)
@chiguabgt10 (8/8 hand-verifiable sample passed)1.0018 hours@chiguabgt (8–2)
@hhn002410 (6/8 hand-verifiable sample passed)1.003 days@hhn0024 (10–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. 468 of the 468 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 1,634 comparable posts for this entry, running 7 August 2026 to 16 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.

  • 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).

Of the group of 8 channels, the one whose matching posts we hold earliest is @dubaixinwen2. 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 17 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.

Channels linked by matching posts

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.

Growth

21,154118,47869,816113,5837 August 202617 November 2026
65 measurements spanning 102 days, net +80,236. 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 6,555–133,077 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
17 Nov 2026, 08:12113,583+401
13 Nov 2026, 22:54113,182+4,039
11 Nov 2026, 03:11109,143-2,332
9 Nov 2026, 12:31111,475-2,036
8 Nov 2026, 06:28113,511+7,272
7 Nov 2026, 00:27106,239-1,495
5 Nov 2026, 20:58107,734-2,656
5 Nov 2026, 00:10110,390-3,856
3 Nov 2026, 21:58114,246+13,473
3 Nov 2026, 00:27100,773-1,031
1 Nov 2026, 21:06101,804-1,541
31 Oct 2026, 18:47103,345-1,447
30 Oct 2026, 21:27104,792-1,435
29 Oct 2026, 18:31106,227-764
28 Oct 2026, 21:35106,991-1,285
27 Oct 2026, 19:30108,276-965
26 Oct 2026, 20:15109,241-1,005
25 Oct 2026, 17:49110,246-607
24 Oct 2026, 17:15110,853-920
23 Oct 2026, 14:44111,773first reading

Engagement

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

ERR · 30 days
3.21%
avg views ÷ 113,583 subscribers
Avg views / post
3,640
513 posts measured
Reaction rate
0.636%
reactions ÷ views · ER floor
Posts in window
578
of 1,934 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. It is computed over the 493 of 513 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held1,934 (7 August 2026 – 16 November 2026)
Views total1,869,574
Reactions total11,416
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 02:52 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
1h 03m
Average length
17s

Measured directly from 221 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

18,857 reactions across 822 posts, in 3 distinct kinds. The most used accounts for 33.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6,33733.6%
👍6,31033.5%
🔥6,21032.9%

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 822 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 18,857 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 29 September 2026 to 16 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 578 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).

16 Nov 2026, 14:49 UTC≈3,810 views26 reactionsread 17 November 2026
Video

🏆🏆🏆🏆🏆🏆 🇻🇳🇻🇪🇻🇳🇻🇳🇻🇪 🩷🩷🩷🩷🩷🩷🩷🩷🩷 🏆 多元游戏 · 一站畅玩 🏆 真人/电子/体育/棋牌/捕鱼/彩票 🏆 每日返水 · 福利不断 🏆 极速出款 · 高效服务 🏆 7×24小时在线客服 🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆 🏆支持认证:点击可查 🌟😍😍😍😍😍😍😍😍😍😍😍 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🌟😍😍😍😍😍😍😍😍😍😍😍 🏆🏆🏆🏆🏆: M8.com 🏆🏆🏆🏆🏆: @m8baby04 🏆🏆🏆🏆🏆: @m8vvip 🩷🩷🩷🩷🩷: @M8COM04_bot

👍10🔥10❤6

16 Nov 2026, 14:48 UTC≈3,400 views23 reactionsread 17 November 2026
Photo

💲 E8 Wallet|娱乐公群/供需正式开放 🌐 开放入驻 · 公平合作 · 中立运营 E8 Wallet 娱乐公群现正式面向各类符合准入要求的商家开放入驻,致力于打造公平、透明、开放的商户交流生态。 ✅ 仅收取月租维护费用 ✅ 不抽流水 · 不收交易佣金 ✅ 无利益挂靠 · 无商业站队 ✅ 独立运营 · 公平对待所有商家 🛡 坚持平台中立,不参与商家经营及收益分配。 我们只提供平台服务,不干预正常商业竞争,让每一位商家都能在公平的环境中发展。 💎 E8 Wallet|以中立立场,构建开放生态。 ━━━━━━━━━━━━━━ 💳 钱包入口:@E8QB 🔰 商户公群:@E8QBGQ 🛍供需频道:@E8QBGX 🤖 备用机器人:@E8WalletBOT 🛠 官方管理:@E8QBadminBOT 🎧 24/7 Support:@E8QBKF 🌐 官方网站:https://www.e8qianbao.com E8 Wa…

❤9🔥8👍6

16 Nov 2026, 14:38 UTC≈3,710 views16 reactionsread 17 November 2026
Video

✨✨✨✨✨✨✨✨✨✨✨✨ ✨✨✨✨✨ tbh682.vip 😄😃😄 😐😐😐😐 ⚡️⚡️⚡️⚡️ 😐下载官方IM 聊天软件 领注册彩金 😐签到7天领最高888元 😐首存100送69/500送288/1000送588 😭首存送/二存送 /三存送送!! 🥲真人视讯8点遇9点领16668元 😐超高返水1.3%洗码无上限 😐商城积分兑游戏币/手机等实物 🎁🎁官方频道:@tbhvip 🤕🤕彩金客服:@tbhkefu ⚡️⚡️⚡️⚡️⚡️: 1️⃣.代理线🥲个有效用户,享🥲😐⭐️佣金分成 2️⃣.代理扶持鼓励金上不封顶 3️⃣.代理享月存送5888彩金/礼品 4️⃣.代理介绍代理永享😐😐😐分红 5️⃣.人头返佣单个100-150元礼金无上限 🤢招商专员: @xiye66 😀官方招商: @tbhcom1

🔥8👍6❤2

16 Nov 2026, 14:34 UTC≈3,530 views17 reactionsread 17 November 2026
Video

X9 Sports |开启便捷投注新纪元 千万奖池 |实力链上可查实力强 独立域名 |彰显代理实力倍有面 游戏最全 |无忧畅玩上千款游戏 三秒返奖 |区块链公平公正可查 [✅广告]X9bet哈希反水2.5%投注笔笔反独立落地页 游戏最全 · 实力雄厚 · 极速体验 · 公平博弈 哈希|体育|轮盘|德州|轮盘|秒合约| 棋牌|真人|电子|彩票|棋牌|加密游戏 咨询最高2%投注反水或78%负盈利待遇 X9哈希观战频道: @x9tygzpd X9唯一官方客服: @x9_bet_xiaoyu X9哈希官方频道: @x9sportsty1 X9体育推单频道: @x9fun X9 哈希AI播报代理裂变机器人

🔥8❤7👍2

16 Nov 2026, 14:33 UTC≈3,410 views18 reactionsread 17 November 2026
Photo

📢 金尊飞投官方公告 🎁 推荐入款方式:USDT-TRC20 为确保您的资金安全、到账快速,推荐使用 USDT-TRC20 入款方式! 👉 单笔充值 1000U以上,还可 额外获得彩金奖励,无门槛赠送,越充越赚! ⚽️金尊飞投: @JZTYWBOT 💸 快捷支付通道:Okpay💰 充值/提现 秒速到账,全自动处理! 点击联系 👉 @okpay 📣 每日红包活动上线中! 关注官方活动频道: 📍 https://t.me/JZFTHD 不定时发送百万红包,笔笔可提现,先到先得!

❤10🔥5👍3

16 Nov 2026, 14:33 UTC≈3,670 views24 reactionsread 17 November 2026
Photo

📢 超级28 公告 🔥 超级28 最新赔率公告 🔥🧧 @CJPC28BOT ━━━━━━━━━━━━━━ 🛡 安全正规 · 实力保障 💰 全网押金超 1000 万美金 🏆 稳定运营 · 资金秒到 · 放心畅玩 ━━━━━━━━━━━━━━ 尊敬的用户: 超级28平台各项功能正常运行,下注、结算、充值、提现均按规则正常执行。 为保障账户安全与处理效率, 充值与提现建议统一通过 BOT 私信模式操作。 如在使用过程中遇到任何问题,请及时联系官方客服人员协助处理。 🔐 平台特性: 安全 · 匿名 · 高效 🎉下注: https://t.me/+BFVXHbBB2HZiZTY1 📡官方频道: @CJPC28 👩‍💻客服频道: @CJPC28KEFU 👮‍♀️双向客服: @CJPC28KFBOT 单日充值 10000U 以上用户 将参与当日 流水王 NO.1 评选 有机会获得官方特别福利奖励 感谢各位用户的支持与理解, 超级…

🔥12👍7❤5

16 Nov 2026, 11:17 UTC≈3,570 views20 reactionsread 17 November 2026
Photo

一顿生日晚餐,竟成最后一聚:一位母亲在富查伊拉车祸中痛失21岁双胞胎儿女与3岁外孙 在富查伊拉交通事故夺走她四个孩子中的两个以及她孙子的生命数日后,阿里法(Arifa)仍在努力接受这场悲剧。“我到现在都不知道发生了什么。”她告诉《Khaleej Times》。 阿里法坐在富查伊拉医院(Fujairah Hospital)里,身旁是她最小的孙子——这名一岁幼儿因腿部骨折正在接受治疗。她旁边,女儿法尔萨娜(Farsana)坐在轮椅上,一只手打着石膏,脸上有淤青。阿里法的侄女法赫米达(Fahmida)陪着她们。 阿里法21岁的双胞胎子女穆罕默德·阿斯米尔(Mohammed Asmil)和米斯纳·朱宾(Misna Jubin),以及她3岁的孙子穆罕默德·法伊兹(Mohammed Fayiz),在乘坐的汽车撞上卡车时不幸身亡。 事发前,一家人送法赫米达回沙迦的家,返程途中遭遇车祸。 “我们在姆莱哈(Mleiha)停下来喝了茶。”…

🔥9👍6❤5

16 Nov 2026, 11:17 UTC≈3,970 views25 reactionsread 17 November 2026
Photo

放假2天!阿联酋宣布私营部门的国庆节假期 阿联酋宣布,为庆祝第55个“联合日”,私营部门员工可享受两天带薪公共假期,假期落在2026年12月2日(周三)和12月3日(周四)。 据UAE Barq发布的公告,人力资源与阿联酋化部(Ministry of Human Resources and Emiratisation)周五(11月13日)确认了假期日期。 🆘🆘 超搜朋友圈🎈@CSZWPYQ 超搜🔍中文搜索 @CSZWBOT 独家赞助 —————————————————————— 🔥欢迎关注【博安新闻】曝光频道⚠️ 🥰 😀😀😀😀 👑 广告合作 @boan110 👨‍💻 投稿曝光 @boantougao

❤9🔥9👍7

16 Nov 2026, 11:17 UTC≈3,790 views25 reactionsread 17 November 2026
Photo

阿联酋位列2026年“幸福护照指数”第23名 阿联酋在2026年“幸福护照指数”(Happy Passports Index)中位列第23名,在满分100分中得73.4分。该指数从生活质量、个人自由、国际通行能力、繁荣、健康与安全等维度进行全球排名。 该指数由国际咨询公司全球公民解决方案公司(Global Citizen Solutions)发布,评估了50个国家,不仅衡量各国护照的含金量,还衡量其居民的生活条件和享有的自由。 阿联酋在国际通行能力方面表现最强,得94.3分,跻身护照通达度最高的国家之列。该国在繁荣、健康与安全方面得74分,幸福感得69.8分,国内自由得55.4分。 🆘🆘 超搜朋友圈🎈@CSZWPYQ 超搜🔍中文搜索 @CSZWBOT 独家赞助 —————————————————————— 🔥欢迎关注【博安新闻】曝光频道⚠️ 🥰 😀😀😀😀 👑 广告合作 …

🔥17❤4👍4

16 Nov 2026, 11:17 UTC≈3,660 views23 reactionsread 17 November 2026
Photo

内政部:再次呼吁遵守交通规则,加强道路安全 内政部再次呼吁所有道路使用者遵守交通规则,遵守限速规定,保持车辆之间的安全距离,留意交通状况变化,尤其是在车流减速或停滞时,并强调遵守交通指引是共同责任,有助于保护生命、加强道路安全。 在富查伊拉酋长国发生一起交通事故后,内政部强调,有必要提高交通安全意识,并在驾驶时遵守安全要求,以减少交通事故,保障道路使用者的安全。 🆘🆘 超搜朋友圈🎈@CSZWPYQ 超搜🔍中文搜索 @CSZWBOT 独家赞助 —————————————————————— 🔥欢迎关注【博安新闻】曝光频道⚠️ 🥰 😀😀😀😀 👑 广告合作 @boan110 👨‍💻 投稿曝光 @boantougao

❤11🔥9👍3

16 Nov 2026, 11:17 UTC≈3,590 viewsread 17 November 2026
Photo

富查伊拉这起致命事故造成14人死亡,其中包括10名阿联酋人和4名印度人 事故原因是卡车司机失控撞上另一辆翻车的车辆。翻车的车辆又撞上了多辆因交通拥堵而停下的车辆。卡车起火后,火势迅速蔓延至其他车辆。 🆘🆘 超搜朋友圈🎈@CSZWPYQ 超搜🔍中文搜索 @CSZWBOT 独家赞助 —————————————————————— 🔥欢迎关注【博安新闻】曝光频道⚠️ 🥰 😀😀😀😀 👑 广告合作 @boan110 👨‍💻 投稿曝光 @boantougao

Showing the 12 most recent of 1,934 posts we hold for @bc123cobg. 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.

Posts recorded as deleted after publishing

We recorded 9 posts on @bc123cobg as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
17 August 2026
Most recent seen missing
21 October 2026
Median time before seen missing
18 hours
Seen missing in the last 30 days
3

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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.

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

“迪拜🇦🇪海湾大事件” (@bc123cobg), 113,583 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/bc123cobg.

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.