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 9 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 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 3 other registered channels. 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)
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
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. 8 of the 8 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,726 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.
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).
Recorded under the key 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.
Growth
64 measurements spanning 95 days, net -55,747. 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 94,174–166,645 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)
Subscribers
Change
10 Nov 2026, 12:15
102,536
-1,966
8 Nov 2026, 22:49
104,502
-544
7 Nov 2026, 12:25
105,046
-1,269
6 Nov 2026, 15:56
106,315
-1,017
5 Nov 2026, 12:18
107,332
-301
4 Nov 2026, 14:37
107,633
-736
3 Nov 2026, 14:59
108,369
-523
2 Nov 2026, 14:46
108,892
-112
1 Nov 2026, 13:36
109,004
-457
31 Oct 2026, 12:44
109,461
-467
30 Oct 2026, 13:11
109,928
-910
29 Oct 2026, 14:08
110,838
-651
28 Oct 2026, 10:05
111,489
-338
27 Oct 2026, 08:38
111,827
-491
26 Oct 2026, 11:09
112,318
-318
25 Oct 2026, 11:27
112,636
-302
24 Oct 2026, 12:04
112,938
-1,108
23 Oct 2026, 14:16
114,046
-952
22 Oct 2026, 14:05
114,998
-1,791
21 Oct 2026, 06:30
116,789
first reading
Engagement
1,755 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 196 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.41%
avg views ÷ 102,536 subscribers
Avg views / post
2,480
455 posts measured
Reaction rate
0.081%
reactions ÷ views · ER floor
Posts in window
455
of 1,755 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 97 of 455 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 11 November 2026
Posts held
1,755 (7 August 2026 – 11 November 2026)
Views total
1,126,305
Reactions total
178
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 04:07 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
≈23,700
Videos
≈4,120
Links
≈21,500
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.
Video runtime
1h 26m
Average length
12s
Measured directly from 426 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
243 reactions across 152 posts, in 12 distinct kinds. The most used accounts for 16.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🥰
41
16.9%
❤
30
12.3%
🎉
27
11.1%
👏
27
11.1%
👍
25
10.3%
🔥
25
10.3%
⚡
24
9.88%
😁
22
9.05%
🤩
19
7.82%
👎
1
0.412%
💩
1
0.412%
🤯
1
0.412%
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 152 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 243 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 13 September 2026 to 11 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: 5 of 455 posts held from the last 30 days (1.10%) 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).
Showing the 12 most recent of 1,755 posts we hold for @kk4568. 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 edited after publishing
@kk4568 edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
25 September 2026
Most recent edit
5 November 2026
Posts recorded as deleted after publishing
We recorded 1 post on @kk4568 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
28 August 2026
Most recent seen missing
28 August 2026
Median time before seen missing
29 hours
Seen missing in the last 30 days
0
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
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 14 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.
迪拜大事件【新闻曝光】 @kz692nn · 123,607 Telegram ranks this channel #1 of 71 here — alongside 70 others — read 15 August 2026
TG第一曝光频道 @tg88f · 117,382 Telegram ranks this channel #5 of 75 here — alongside 74 others — read 15 August 2026
今日头条 @huarentt · 54,401 Telegram ranks this channel #6 of 19 here — alongside 18 others — read 2 September 2026
东南亚大事件丨78.com冠名 @w1666 · 35,267 Telegram ranks this channel #7 of 64 here — alongside 63 others — read 23 August 2026
东南亚安危曝光|西港日记 @ZYWX6 · 86,382 Telegram ranks this channel #7 of 69 here — alongside 68 others — read 22 August 2026
吃瓜新闻 @chiguaxinwen1 · 22,111 Telegram ranks this channel #8 of 20 here — alongside 19 others — read 26 September 2026
AI短剧 吃瓜 搞笑 美女🎉 @chigu0777 · 52,301 Telegram ranks this channel #8 of 22 here — alongside 21 others — read 29 August 2026
生活素材包装【阿Q资讯】 @AQzx_7 · 67,400 Telegram ranks this channel #10 of 42 here — alongside 41 others — read 23 August 2026
🇦🇪迪拜大事件/东南亚新闻 @YYL333 · 105,699 Telegram ranks this channel #10 of 66 here — alongside 65 others — read 17 August 2026
迪拜新闻大事件 @uae918 · 75,443 Telegram ranks this channel #10 of 67 here — alongside 66 others — read 16 August 2026
博彩黑平台曝光🔍 @uuuuuf · 171,017 Telegram ranks this channel #11 of 82 here — alongside 81 others — read 17 August 2026
全球资讯曝光大事件 @nnccqq · 37,485 Telegram ranks this channel #13 of 23 here — alongside 22 others — read 31 August 2026
🇦🇪迪拜大事件I九尾曝光I全球新闻IDuBai生活资讯攻略🇦🇪 @Dubai1817 · 117,523 Telegram ranks this channel #13 of 27 here — alongside 26 others — read 18 August 2026
头条大事件 @alqxzs · 45,259 Telegram ranks this channel #14 of 24 here — alongside 23 others — read 28 August 2026
东南亚大事件|海外事件|吃瓜曝光|今日头条 @miandianDS · 41,602 Telegram ranks this channel #14 of 50 here — alongside 49 others — read 27 August 2026
新闻大事件【阿Q资讯】 @AQzx_1 · 148,677 Telegram ranks this channel #14 of 72 here — alongside 71 others — read 14 August 2026
吃瓜驿站😋🍉 @DNYQWCG · 73,512 Telegram ranks this channel #15 of 57 here — alongside 56 others — read 19 August 2026
迪拜新闻|华人资讯曝光|dubai news @Dubaihuarenzixun · 64,320 Telegram ranks this channel #21 of 73 here — alongside 72 others — read 18 August 2026
东南亚大事件|头条新闻 @abc03 · 203,877 Telegram ranks this channel #21 of 34 here — alongside 33 others — read 17 August 2026
东南亚大事件|柬埔寨新闻|头号玩家生活资讯 @dny12378 · 66,417 Telegram ranks this channel #22 of 68 here — alongside 67 others — read 18 August 2026
缅甸新闻头条 @hyxw4 · 55,150 Telegram ranks this channel #23 of 55 here — alongside 54 others — read 19 August 2026
曝光骗子 @baoguang2022 · 128,797 Telegram ranks this channel #24 of 76 here — alongside 75 others — read 15 August 2026
全球大事件曝光❖东南亚吃瓜新闻 @dsj665 · 116,519 Telegram ranks this channel #26 of 72 here — alongside 71 others — read 15 August 2026
东南亚新闻头条(曝光) @dnyxwtt · 51,723 Telegram ranks this channel #27 of 79 here — alongside 78 others — read 24 August 2026
This channel appears in 50 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.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“迪拜黑料大曝光” (@kk4568), 102,536 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/kk4568.
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.