[Trang Mới QZ88 Thuộc Cổng V8] ⚡️Làm Nhiệm Vụ Nhận Thưởng đến 58k ➡️Link Chuẩn https://bom.so/QZ88 🥰Nạp Đầu Đang Auto 500k+188k ÉT Cam Kết Rút Về ae yên tâm chơi✨
❤1

Channel
@khuyenmainhacai22
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
24,469subscribers
-1,365 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002183424402 |
|---|---|
| Type | Channel |
| Username | @khuyenmainhacai22 |
| Description | 🎁Trò Chuyện @maxwinmoingay CỘT MỐC 29/4/2025 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 68 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/khuyenmainhacai22 |
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 10 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.
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 in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @codefreeapp/71512 Sept 2026, 01:01 UTC | @khuyenmainhacai22/8854 · this entry2 Sept 2026, 15:56 UTC | 1.00 | 15 hours |
| @codefreeapp/716125 Sept 2026, 00:25 UTC | @khuyenmainhacai22/8863 · this entry25 Sept 2026, 05:40 UTC | 1.00 | 5.3 hours |
| @codefreeapp/71715 Oct 2026, 15:38 UTC | @khuyenmainhacai22/8871 · this entry5 Oct 2026, 17:13 UTC | 1.00 | 1.6 hours |
| @codefreeapp/717814 Oct 2026, 21:59 UTC | @khuyenmainhacai22/8877 · this entry14 Oct 2026, 23:29 UTC | 1.00 | 1.5 hours |
| @codefreeapp/718121 Oct 2026, 00:31 UTC | @khuyenmainhacai22/8880 · this entry21 Oct 2026, 11:57 UTC | 1.00 | 11 hours |
| @chiasesangame/527021 Oct 2026, 19:29 UTC | @khuyenmainhacai22/8881 · this entry22 Oct 2026, 00:33 UTC | 1.00 | 5.1 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @codefreeapp | 23 (8/8 hand-verifiable sample passed) | 1.00 | 4.8 hours | @codefreeapp (23–0) |
| @chiasesangame | 6 (6/6 hand-verifiable sample passed) | 1.00 | 11 hours | @chiasesangame (6–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. 28 of the 28 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 44 comparable posts for this entry, running 14 June 2026 to 14 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.
Of the group of 3 channels, the one whose matching posts we hold earliest is @codefreeapp. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 15 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.
This channel is in a group of 3 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 00:49 | 24,469 | -69 |
| 12 Nov 2026, 15:20 | 24,538 | -26 |
| 10 Nov 2026, 09:58 | 24,564 | -31 |
| 8 Nov 2026, 18:22 | 24,595 | -30 |
| 7 Nov 2026, 11:28 | 24,625 | -8 |
| 6 Nov 2026, 09:09 | 24,633 | -13 |
| 5 Nov 2026, 11:09 | 24,646 | -24 |
| 4 Nov 2026, 14:20 | 24,670 | -7 |
| 3 Nov 2026, 12:39 | 24,677 | -4 |
| 2 Nov 2026, 15:10 | 24,681 | -23 |
| 1 Nov 2026, 12:20 | 24,704 | -14 |
| 31 Oct 2026, 10:00 | 24,718 | -13 |
| 30 Oct 2026, 13:31 | 24,731 | -13 |
| 29 Oct 2026, 15:01 | 24,744 | -22 |
| 28 Oct 2026, 12:14 | 24,766 | -21 |
| 27 Oct 2026, 11:57 | 24,787 | -20 |
| 26 Oct 2026, 12:45 | 24,807 | -9 |
| 25 Oct 2026, 13:06 | 24,816 | -10 |
| 24 Oct 2026, 11:41 | 24,826 | -9 |
| 23 Oct 2026, 09:01 | 24,835 | first reading |
49 posts held, back to 14 June 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 150 pages of 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 4 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 49 (14 June 2026 – 14 November 2026) |
| Views total | 2,534 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 03:56 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.
Lifetime counters from Telegram’s own channel header, read 18 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.
Measured directly from 1 video 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.
16 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 93.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 93.8% | |
| 👎 | 1 | 6.25% |
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 15 of the 49 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 49 most recent posts we hold, published 14 June 2026 to 14 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.
Telegram’s own ‘edited’ marker: 0 of 10 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).
[Trang Mới QZ88 Thuộc Cổng V8] ⚡️Làm Nhiệm Vụ Nhận Thưởng đến 58k ➡️Link Chuẩn https://bom.so/QZ88 🥰Nạp Đầu Đang Auto 500k+188k ÉT Cam Kết Rút Về ae yên tâm chơi✨
❤1
Thứ 6 Ngày 13 hạn chế chơi cờ bạc nha ae 😂 😀Ae vô tổng kênh nhóm nè @maxwinmoingay
QQ79 thưởng nạp mỗi ngày nhận đến 38m nè ae nay tui nạp cx thưởng hơn 6 lít ⚫️Thưởng nạp này tri ân mỗi ngày nha ⭐️Nạp Đầu TẶNG ĐẾN 18,888K nạp 200k+188k này hên xui còn nạp kia thấy dễ kìa ➡️Link Chuẩn: https://bom.so/QQ79 ➡️Link GR: @maxwinmoingay 🏆ae mà chơi to vô con này nhận thưởng nạp ổn - có top cược hũ cá top 1 38,888 👆
[Trang Mới UW88 UY TÍN] ⚫️Nạp Đầu 200k+138k X3 Hũ Cá ⚫️Tải App Nhận 58k Khi Nạp Đủ 500k 😍Trang mới ra nạp rút uy tín quay kbt nhả ko ae trải nghiệm ➡️Link Chính https://bom.so/UW88_ ➡️Link Phụ https://sl1nk.com/up2puln ❣️ Link GR Chat @maxwinmoingay
Tích tiểu thành đại nha ae tui nhiêu là nghỉ đc r trang mới E39 rút nhanh có free 58k LINK GR 💭 @maxwinmoingay
❤1👎1
[Trang Mới E39 Free 58K ] ⚫️58K free X10 vòng hũ cá max 300K. ⚫️Nạp Đầu 500k+188k X3 All game Có Thể Chơi Casino ➡️Link Chuẩn https://bom.so/E39 LINK GR 💭 @maxwinmoingay
❤1
[Trang Mới KK8 Free 68K] ⚫️Tri ân 68K Free x10 VC Hũ Cá ⚫️Nạp Đâu 500k+188k x2 ALL Game ➡️Link Chuẩn https://bom.so/KK8 🏆Thuê SMS bào sll @sangamepros1_bot LINK GR 💭 @maxwinmoingay
❤1
[JU88 Trang Mới Nạp Đầu Mới ra dễ lên bào vội] ⚫️Khuyến mãi nạp đầu lên ngon nhé ae 100k+58k⚫️1m+288k ➡️Link Chuẩn https://bom.so/JU88 😂Vòng cược hơi cao đọc kĩ km trc khi tham gia 🙏 LINK GR 💭 @maxwinmoingay
[V79 Tân thủ 58K Ae test xem còn lên k nha] ⚫️Đăng ký tặng 58K 100k Rút Nạp đầu 500+188 x3 vòng cược ➡️ Link: https://bom.so/V79_ LINK GR 💭 @maxwinmoingay
Anh em có nạp 88iBET thì vào nhận lixi bí ẩn ngày 20 nha. Ngoài ra có thể nạp chơi để nhận thêm khuyến mãi hoàn nạp mỗi ngày. ➡️Link: https://bom.so/88ibet_ 🏆Tham Gia ngay @maxwinmoingay
Trang FV88 phát rồi anh em vào nhận đi.Ráng x5 cược tổng nạp để nhận thêm hoàn nạp vào sáng mai nữa nha cược nhiều nhận hoàn trả + lì xì chóng cháy khá ngon ➡️Link FV88 https://bom.so/fv88_1 ➡️Link 88ibet https://bom.so/88ibet_1 ⚫️Chat đây @maxwinmoingay
[ TRANG MỚI VAN88 Hệ Nhà Go99 NOHU] ⚫️Đang Có Free Tải App 50K ⚫️200K+188kNạp 500k+228k ➡️Truy Cập https://bom.so/Van88 Chat 😎 @maxwinmoingay
Showing the 12 most recent of 49 posts we hold for @khuyenmainhacai22. 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.
@khuyenmainhacai22 edited 3 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.
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.
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.
@khuyenmainhacai22 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“Tổng Hợp Khuyến Mãi Free🍎” (@khuyenmainhacai22), 24,469 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/khuyenmainhacai22.
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.