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 11 August 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 why it has no browse page of its own yet.
Growth
29 measurements spanning 38 days, net +15,579. 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 149,872–193,097 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)
Subscribers
Change
18 Sept 2026, 20:36
180,161
-3,722
16 Sept 2026, 12:41
183,883
+1,438
14 Sept 2026, 15:18
182,445
+9,246
13 Sept 2026, 04:01
173,199
-5,386
11 Sept 2026, 02:57
178,585
-3,484
8 Sept 2026, 06:40
182,069
-4,186
5 Sept 2026, 04:16
186,255
-1,854
3 Sept 2026, 10:44
188,109
+13,356
2 Sept 2026, 05:47
174,753
+3,570
1 Sept 2026, 09:03
171,183
-458
31 Aug 2026, 12:24
171,641
-536
30 Aug 2026, 10:07
172,177
-2,318
29 Aug 2026, 07:06
174,495
-1,688
28 Aug 2026, 06:03
176,183
-523
27 Aug 2026, 03:32
176,706
-952
26 Aug 2026, 06:02
177,658
-1,404
25 Aug 2026, 07:57
179,062
-1,253
24 Aug 2026, 08:53
180,315
-1,399
22 Aug 2026, 17:25
181,714
-1,630
21 Aug 2026, 08:33
183,344
first reading
Engagement
756 posts held, back to 11 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 83 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.256%
avg views ÷ 180,161 subscribers
Avg views / post
462
509 posts measured
Reaction rate
0.752%
reactions ÷ views · ER floor
Posts in window
509
of 756 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 293 of 509 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 22 September 2026
Posts held
756 (11 August 2026 – 22 September 2026)
Views total
234,920
Reactions total
820
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Sept 2026, 07:28 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
Photos
≈16,100
Videos
≈2,880
Links
≈8,100
Lifetime counters from Telegram’s own channel header, read 22 September 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.
Video runtime
1h 23m
Average length
22s
Measured directly from 222 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
1,102 reactions across 426 posts, in 9 distinct kinds. The most used accounts for 13.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
143
13.0%
👏
131
11.9%
🔥
124
11.3%
⚡
121
11.0%
😁
120
10.9%
👍
118
10.7%
🤩
116
10.5%
🥰
116
10.5%
🎉
113
10.3%
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 426 of the 756 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,102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 756 most recent posts we hold, published 11 August 2026 to 22 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.
Showing the 12 most recent of 756 posts we hold for @dubai1w. 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
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.
Channels Telegram recommends alongside this 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.
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.
吃瓜中心🍉内涵段子 @chiguazhongxin3 · 149,211 Telegram ranks this channel #2 of 25 here — alongside 24 others — read 17 August 2026
🇦🇪迪拜大事件I九尾曝光I全球新闻IDuBai生活资讯攻略🇦🇪 @Dubai1817 · 52,390 Telegram ranks this channel #3 of 27 here — alongside 26 others — read 18 August 2026
迪拜/东南亚/大事件曝光生活资讯攻略 @tingyu0002 · 212,208 Telegram ranks this channel #4 of 27 here — alongside 26 others — read 11 August 2026
迪拜大事件|迪拜新闻|Dubai生活资讯攻略 @dubai0 · 77,364 Telegram ranks this channel #6 of 25 here — alongside 24 others — read 19 August 2026
迪拜新闻|华人资讯曝光|dubai news @Dubaihuarenzixun · 67,684 Telegram ranks this channel #6 of 73 here — alongside 72 others — read 18 August 2026
头条大事件 @alqxzs · 49,097 Telegram ranks this channel #9 of 24 here — alongside 23 others — read 28 August 2026
🌏迪拜新闻曝光-安危头条🇦🇪迪拜通🔥 @dibaiTT · 194,738 Telegram ranks this channel #10 of 41 here — alongside 40 others — read 12 August 2026
🥇东南亚华人大事件 @DNY88880 · 91,312 Telegram ranks this channel #11 of 53 here — alongside 52 others — read 19 August 2026
🌏泰国新闻曝光-攻略头条🔥 @taiguopindao · 139,529 Telegram ranks this channel #11 of 27 here — alongside 26 others — read 12 August 2026
东南亚大事件|柬埔寨新闻|头号玩家生活资讯 @dny12378 · 97,053 Telegram ranks this channel #14 of 68 here — alongside 67 others — read 18 August 2026
东南亚大事件 @w1666 · 102,034 Telegram ranks this channel #26 of 64 here — alongside 63 others — read 23 August 2026
东南亚安危曝光|西港日记 @ZYWX6 · 101,169 Telegram ranks this channel #26 of 69 here — alongside 68 others — read 22 August 2026
迪拜新闻大事件 @uae918 · 91,667 Telegram ranks this channel #32 of 67 here — alongside 66 others — read 16 August 2026
缅甸新闻头条 @hyxw4 · 77,008 Telegram ranks this channel #34 of 55 here — alongside 54 others — read 19 August 2026
🇦🇪迪拜大事件/东南亚新闻 @YYL333 · 96,484 Telegram ranks this channel #34 of 66 here — alongside 65 others — read 17 August 2026
迪拜大事件 @AQzx_3 · 93,113 Telegram ranks this channel #35 of 62 here — alongside 61 others — read 13 August 2026
迪拜 东南亚求职招聘 @Dubaiqzzp · 92,515 Telegram ranks this channel #57 of 64 here — alongside 63 others — read 17 August 2026
🇦🇪迪拜求职招聘 @dibaidddd · 120,900 Telegram ranks this channel #57 of 70 here — alongside 69 others — read 13 August 2026
迪拜大事件【新闻曝光】 @kz692nn · 139,774 Telegram ranks this channel #66 of 71 here — alongside 70 others — read 15 August 2026
This channel appears in 19 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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“东南亚” (@dubai1w), 180,161 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/dubai1w.
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.