11 measurements spanning 11 days, net +1,696. 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 48,227–54,805 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 15:55
51,551
-444
21 Aug 2026, 09:57
51,995
-219
20 Aug 2026, 07:38
52,214
-322
19 Aug 2026, 09:24
52,536
-413
18 Aug 2026, 12:43
52,949
-503
17 Aug 2026, 15:07
53,452
-594
16 Aug 2026, 05:05
54,046
+5,060
14 Aug 2026, 13:36
48,986
-400
13 Aug 2026, 06:04
49,386
-386
12 Aug 2026, 04:12
49,772
-83
11 Aug 2026, 20:45
49,855
first reading
Engagement
169 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 21 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
0.022%
avg views ÷ 51,551 subscribers
Avg views / post
11.6
169 posts measured
Reaction rate
63.4%
reactions ÷ views · ER floor
Posts in window
169
of 169 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 145 of 169 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 August 2026
Posts held
169 (11 August 2026 – 22 August 2026)
Views total
1,958
Reactions total
1,137
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 13:58 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
36m 10s
Average length
36s
Measured directly from 60 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,137 reactions across 145 posts, in 14 distinct kinds. The most used accounts for 14.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👏
166
14.6%
🤩
152
13.4%
👍
151
13.3%
🔥
150
13.2%
🥰
132
11.6%
😁
128
11.3%
⚡
123
10.8%
🎉
120
10.6%
❤
4
0.352%
👾
4
0.352%
🦄
3
0.264%
🤡
2
0.176%
😨
1
0.088%
🙉
1
0.088%
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 145 of the 169 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,137reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 169 most recent posts we hold, published 11 August 2026 to 22 August 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 169 posts we hold for @DB405. 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.
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.
东南亚大事件|曝光|悬赏|投稿🏆 @dyy83 · 111,643 Telegram ranks this channel #4 of 69 here — alongside 68 others — read 14 August 2026
菲律宾大事件 @PHDA15 · 97,915 Telegram ranks this channel #10 of 75 here — alongside 74 others — read 15 August 2026
柬埔寨大事件🇰🇭西港日记 @xinwenhc · 30,722 Telegram ranks this channel #24 of 67 here — alongside 66 others — read 15 August 2026
今日聚焦曝光 @a0159 · 127,650 Telegram ranks this channel #26 of 67 here — alongside 66 others — read 13 August 2026
东南亚(有话说)|曝光日记 @db933 · 195,379 Telegram ranks this channel #26 of 65 here — alongside 64 others — read 11 August 2026
马来西亚新闻|华人资讯曝光|malaysia news @malaixiyahuarenzixun · 74,874 Telegram ranks this channel #38 of 78 here — alongside 77 others — read 17 August 2026
东南亚🇨🇿今日头条 @huohu158 · 30,733 Telegram ranks this channel #40 of 74 here — alongside 73 others — read 15 August 2026
柬埔寨新闻头条 @hyxw3 · 75,948 Telegram ranks this channel #49 of 76 here — alongside 75 others — read 19 August 2026
头条快报 @ttkb0 · 113,919 Telegram ranks this channel #50 of 77 here — alongside 76 others — read 14 August 2026
全球华人新闻吃瓜头条大曝光 @dnyqqbj · 116,274 Telegram ranks this channel #51 of 72 here — alongside 71 others — read 14 August 2026
泰国新闻|华人资讯曝光|thailand news @taiguohuarenzixun · 84,393 Telegram ranks this channel #55 of 71 here — alongside 70 others — read 15 August 2026
东南亚新闻/黑料曝光 @BG6668 · 99,125 Telegram ranks this channel #56 of 57 here — alongside 56 others — read 14 August 2026
老挝新闻|华人资讯曝光|laos news @laowohuarenzixun · 78,309 Telegram ranks this channel #60 of 74 here — alongside 73 others — read 16 August 2026
东南亚大事件·news channel @gejige · 39,096 Telegram ranks this channel #61 of 77 here — alongside 76 others — read 15 August 2026
东南亚新闻|斑马曝光|news @Banma_xinwen · 96,322 Telegram ranks this channel #64 of 77 here — alongside 76 others — read 16 August 2026
泰国大事件 @dnyxst · 91,125 Telegram ranks this channel #69 of 80 here — alongside 79 others — read 17 August 2026
缅甸新闻|华人资讯曝光|myanmar news @miandianhuarenzixun · 78,926 Telegram ranks this channel #72 of 77 here — alongside 76 others — read 16 August 2026
东南亚新闻💎 @vipn8888 · 80,158 Telegram ranks this channel #73 of 79 here — alongside 78 others — read 18 August 2026
Тенденции эпохи @eratrends · 137,295 Telegram ranks this channel #83 of 89 here — alongside 88 others — read 13 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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“迪拜华人大事件|新闻|曝光” (@DB405), 51,551 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/DB405.
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.