🤩🤩🤩🤩🤩 Free 88K All Game Max Rút 300K ❤️❤️❤️❤️❤️ https://www.ks168e.com/?r=tjx5196 💻 BÚ LẸ AE KẺO FIX💻
❤1

Channel
@quandaoxabo2
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,341subscribers
+314 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003693775365 |
|---|---|
| Type | Channel |
| Username | @quandaoxabo2 |
| Created | Between 1 December 2025 and 30 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/quandaoxabo2 |
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.
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 word for word on 1 other registered channel. 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 |
|---|---|---|---|
| @huongdan05/28120 Jul 2026, 11:07 UTC | @quandaoxabo2/126 · this entry20 Jul 2026, 11:08 UTC | 1.00 | under a minute |
| @huongdan05/29025 Jul 2026, 03:01 UTC | @quandaoxabo2/135 · this entry25 Jul 2026, 03:01 UTC | 1.00 | under a minute |
| @quandaoxabo2/141 · this entry27 Jul 2026, 08:08 UTC | @huongdan05/29627 Jul 2026, 08:08 UTC | 1.00 | under a minute |
| @huongdan05/2991 Aug 2026, 12:45 UTC | @quandaoxabo2/144 · this entry1 Aug 2026, 12:47 UTC | 1.00 | 2 minutes |
| @quandaoxabo2/146 · this entry2 Aug 2026, 14:19 UTC | @huongdan05/3012 Aug 2026, 14:19 UTC | 1.00 | under a minute |
| @huongdan05/3127 Aug 2026, 08:39 UTC | @quandaoxabo2/154 · this entry7 Aug 2026, 08:39 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @huongdan05 | 12 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @huongdan05 (8–4) |
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 of the 7 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 12 comparable posts for this entry, running 13 July 2026 to 7 August 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.
Across the whole group of 2, the earliest publisher we hold is @huongdan05. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 8 August 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’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 11 Aug 2026, 23:09 | 4,341 | +221 |
| 8 Aug 2026, 23:03 | 4,120 | +93 |
| 8 Aug 2026, 01:35 | 4,027 | first reading |
18 posts held, back to 13 July 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 1 pageof 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 12 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 18 (13 July 2026 – 7 August 2026) |
| Views total | 11,480 |
| Reactions total | 34 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 01:35 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.
34 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 76.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 26 | 76.5% | |
| 🥰 | 4 | 11.8% | |
| 🎉 | 3 | 8.82% | |
| 🔥 | 1 | 2.94% |
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 12 of the 18 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 34reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 July 2026 to 7 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.
🤩🤩🤩🤩🤩 Free 88K All Game Max Rút 300K ❤️❤️❤️❤️❤️ https://www.ks168e.com/?r=tjx5196 💻 BÚ LẸ AE KẺO FIX💻
❤1
🔥🔥🔥 7️⃣🔠🔡🔡🔡 🧧 GAME MỚI RA MẮT TẢI APP NHẬN 100K X1 VÒNG CƯỢC 🔄 ❤️❤️❤️❤️:https://www.ubenya.com?fid=92508017 ❤️ TẢI APP VỀ LÀ CÓ 100K KO CẦN XIN XỎ , CHỜ ĐỢI ✔️ RÚT TIỀN KO CẦN NẠP ✔️ 1 SỐ ĐIỆN THOẠI ĐƯỢC NHẬN CODE 100K 1 LẦN ( TRÙNG IP VẪN NHẬN ĐƯỢC ) ✔️ CODE GAME CHƠI ĐƯỢC QUAY HŨ VÀ BẮN CÁ X 1 VÒNG CƯỢC ⚠️ LƯU Ý : LIÊN KẾT SĐT TRƯỚC RỒI MỚI CHƠI NHÉ
❤1
🔥 APP MỚI RA TẶNG 100K ✔️ 🔗🔗🔗🔗https://www.yhgena.com?fid=98387822 👉🏻 TẢI APP 👉🏻 NHẤP VÀO AVARTAR LIÊN KẾT SĐT 👉🏻 LIÊN KẾT SĐT MỚI RÚT ĐƯỢC 👉🏻 APP TỰ CỘNG TIỀN ( ✅ X1 ALLGAME ) 💵 Rút ko nạp 3 giây tiền về
✅COMACPRO✅ TẶNG 260K RÚT VỀ TÀI KHOẢN 💰 🔴LINK: https://web.salenet.vn/signup?referral=0379522724 🌟Đăng ký tài khoản (Kiểm tra mật khẩu ở tin nhắn Zalo) 🌟Tải APP + KYC (Trên 18t) 🌟Làm theo hướng dẫn của APP để hoàn thành hồ sơ đăng ký 🖥Nhớ ký hợp đồng để nhận 260K 📣Mời 1 bạn đăng ký nhận 100k 🏦 Rút về Ngân hàng
❤1
😚 Thu acc tele 40k-100k /1 acc ai bán ib @pipit007 🤔 Acc lâu năm , đã tham gia nhiều nhóm sẽ được giá cao
🆒Tải áp tặng free 58k ✔️Km nạp 188+188 X1 vòng cược duyệt auto lên 💥http://www.kk55.live/?r=ytj3408
✅Bot kiếm tiền Casino Live miễn phí vừa ra mắt siêu uy tín 🔵Link Bot:https://t.me/forex959_bot?start=r6229501390 ✅Mời 1 bạn tham gia Bot nhận ngay 5000 VND ✅Min rút: 50k VND 💯Rút về tất cả các ngân hàng có trên lãnh thổ Việt Nam📥 ❌CẤM CÁC HÀNH VI CHEAT, BUFF‼️
❤5🥰2🎉1
😚 Thu acc tele 40k-100k /1 acc ai bán ib @pipit007 🤔 Acc lâu năm , đã tham gia nhiều nhóm sẽ được giá cao
🌟🌟🌟🌟 NHÀ CÁI MỚI NHÀ CÁI MỚI - BÀO FREE BÀO FREE 🌟🌟🌟TẶNG 38K X10 VÒNG NỔ HŨ BẮN CÁ (MIN RÚT 100K VÀ MAX RÚT 500K) 😀😀😀😀😀😀 888K https://888k98.co/?id=401982288
❤2
➡️CÁC TRANG MỚI KHUYẾN MÃI DỄ NHẬN 🥵KHUYẾN MÃI HỦ CÁ 100 + 88 🧐KM ALL GAME X3VC ( TRỪ XỔ SỐ ) ✔️ 100 + 38 / 100 + 68 ✔️500 + 128 / 500 + 138 CHÚ Ý: nạp điền số tiền và tích vào km ⭐⭐⭐⭐⭐http://www.pe7890.com/?r=ojz5930 🤩🤩🤩🤩http://www.pp881.bet/?r=ste2077 😀😀😀😀🐠https://www.m001.game/?id=570272312
🔥 BOT CẤP CODE RÚT TIỀN VỀ STK ✔️ Mời Bạn Bè 1ref = 1.000 VND 💵 Min Rút Tiền Chỉ Từ 10K 🧡 Code Game , Kèo Game Hot 🚀 Tham Gia Ngay Để Kiếm Tiền Free 🤜 Link Bot : @forex959_bot
❤1
Rút tiền 1 giây là về ❤️ 🔗🔗🔗🔗 https://playbb.fun/u/28765689 Chơi game kiếm tiền miễn phí, Mời 1f = 10-26k 💵 Rút Về Ngân Hàng, Paypal ✅ Ngon đấy ae băm lẹ, nhớ chỉnh tuổi trên 23 tuổi mới kiếm được tiền
❤2
Showing the 12 most recent of 18 posts we hold for @quandaoxabo2. 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.
Citation-graph rank — 1,032,669 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Quần Đảo Xa Bờ 🎰” (@quandaoxabo2), 4,341 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/quandaoxabo2.
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.