Telegram RegisterThe public register of Telegram
Telegram profile photo for Z O 8 8 - Vô Là Thắng

Channel

Z O 8 8 - Vô Là Thắng

@zo88chinhhang

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

5,004subscribers

-244 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002555870805
TypeChannel
Username@zo88chinhhang
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/zo88chinhhang

Topic

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.

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 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.

Matching posts — open both and compare (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zo88chinhhang/1002 · this entry6 Aug 2026, 06:55 UTC@eventphatcode1/5176 Aug 2026, 06:56 UTC1.0072 seconds
@zo88chinhhang/1003 · this entry6 Aug 2026, 06:56 UTC@eventphatcode1/5186 Aug 2026, 06:57 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@eventphatcode16 (6/6 hand-verifiable sample passed)1.004 minutesthis entry (51)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 29 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.

  • 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).

Across the whole group of 2, the earliest publisher we hold is @zo88chinhhang — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 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.

Also posting the same content

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.

Growth

5,0045,2495,126.57 August 2026 — 5,248 subscribers7 August 2026 — 5,249 subscribers11 August 2026 — 5,234 subscribers14 August 2026 — 5,215 subscribers16 August 2026 — 5,184 subscribers19 August 2026 — 5,162 subscribers23 August 2026 — 5,152 subscribers26 August 2026 — 5,133 subscribers29 August 2026 — 5,118 subscribers1 September 2026 — 5,095 subscribers6 September 2026 — 5,063 subscribers11 September 2026 — 5,039 subscribers14 September 2026 — 5,023 subscribers19 September 2026 — 5,004 subscribers7 August 202619 September 2026
14 measurements spanning 42 days, net -244. 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 4,967–5,286 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 04:395,004-19
14 Sept 2026, 16:205,023-16
11 Sept 2026, 05:395,039-24
6 Sept 2026, 06:185,063-32
1 Sept 2026, 15:355,095-23
29 Aug 2026, 12:465,118-15
26 Aug 2026, 16:335,133-19
23 Aug 2026, 14:185,152-10
19 Aug 2026, 20:355,162-22
16 Aug 2026, 22:135,184-31
14 Aug 2026, 00:265,215-19
11 Aug 2026, 03:215,234-15
7 Aug 2026, 21:325,249+1
7 Aug 2026, 19:485,248first reading

Engagement

22 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 22 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

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 2 of the 22 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 29 July 2026 to 11 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.

Recent posts

11 Aug 2026, 10:02 UTC36 viewsread 12 August 2026
Photo

😊😊😊 1⃣2⃣3⃣4⃣5⃣6⃣7⃣ 😊😊😊🤨🤪😝😍😁😄😄🥰 😊😊😊 NẠP 🤩🤩🤩🤩 - SĂN THƯỞNG 🤩🤩🤩🤩 😊😊😊 🔥 NHIỀU ANH EM ĐÃ NHẬN THƯỞNG - KIỂM TRA TÀI KHOẢN ZO88 NGAY 🔥 🤩🤩🤩🤩🤩🔜: TẠI ĐÂY 🔥 Chương trình hot nhất mùa WC quay trở lại - anh em xem ngay nhận 1,000,000 liền tay ✅ 1⃣0⃣0⃣🔤 người hoàn thành nhiệm vụ đều có thưởng. ✅ Thưởng nhận xong rút ngay, KHÔNG yêu cầu vòng cược. Sự kiện đặc biệt diễn ra trên Mobile / App, quý khách vui lòng trải nghiệm

9 Aug 2026, 07:40 UTC192 viewsread 12 August 2026
Photo

1⃣2⃣3⃣4⃣5⃣6⃣7⃣ |🌟🌟🌟🌟🌟🌟🌟🌟 🚨 CHÀO SÂN TÂN THỦ – QUÀ TẶNG GẤP BA 🚨 😀😀😀😀😀😀😀😀 https://rebrand.ly/atmzo88 Chỉ cần đăng ký tài khoản mới, anh em sẽ nhận ngay combo 3 ưu đãi cực khủng mùa AFF CUP: 🔣🔣🔣🔣🔣🔣🔣🔣 😊 Đăng ký mới nhận ngay 100K 😊 Nạp đầu thưởng đến 100% 😊 Chuỗi nhiệm vụ cược 100k - thưởng 100M 😖 Một lần đăng ký – Ba lần nhận quà 🌟 Tân thủ vào sân – Quà khủng liền tay ❤❤❤❤❤❤❤❤❤ 🏆 ZO88 OFFICIAL 📱 @nhacaizo88 📱 @z

7 Aug 2026, 17:21 UTC251 viewsread 12 August 2026
Photo

⚠️ QUAN TRỌNG - ZO88 THÔNG BÁO CẬP NHẬT TÊN MIỀN ⚠️ Từ ngày 0️⃣8️⃣➖0️⃣8️⃣➖2️⃣0️⃣2️⃣6️⃣, hệ thống Zo88 chính thức cập nhật tên miền mới. 😊 🔤🔤8️⃣8️⃣🔤🔤🔤🔤 🍬 Lưu ý: 🫢 Hãy cập nhật lại đường dẫn để tránh truy cập nhầm trang giả mạo. 🫢 Các tính năng và dữ liệu tài khoản được giữ nguyên, không bị ảnh hưởng. 🫢 Mọi thông báo mới sẽ được cập nhật liên tục tại kênh chính thức. Trân trọng thông báo! ❤️❤️❤️❤️❤️❤️❤️❤️❤️ 🏆 ZO8

7 Aug 2026, 12:34 UTC212 viewsread 12 August 2026
Photo

⚠ QUAN TRỌNG - ZO88 THÔNG BÁO CẬP NHẬT TÊN MIỀN ⚠ Từ ngày 0⃣7⃣➖0️⃣8️⃣➖2⃣0⃣2⃣6⃣, hệ thống Zo88 chính thức cập nhật tên miền mới. 😊 🔤🔤8⃣8⃣🔤🔤🔤🔤 🍬 Lưu ý: 🫢 Hãy cập nhật lại đường dẫn để tránh truy cập nhầm trang giả mạo. 🫢 Các tính năng và dữ liệu tài khoản được giữ nguyên, không bị ảnh hưởng. 🫢 Mọi thông báo mới sẽ được cập nhật liên tục tại kênh chính thức. Trân trọng thông báo! ❤❤❤❤❤❤❤❤❤ 🏆 ZO88 OFFICIAL 📱 @nhaca

7 Aug 2026, 12:22 UTC57 viewsread 12 August 2026
Photo

🔥 ĐẠI CHIẾN GIÀNH VÉ BÁN KẾT AFF CUP! 🗓 20:00 | 07/08 🇸🇬 Singapore 🆚 Indonesia 🇮🇩 🚨 Singapore thiếu Kyoga Nakamura vì treo giò. ⚔️ Indonesia buộc phải thắng. 🤝 Singapore chỉ cần hòa để đi tiếp. 💥 Dự đoán tỷ số📲 Cổ vũ cùng ZO88! 🏆 ZO88 OFFICIAL 📱@nhacaizo88 📱@zo88chinhhang ❤️❤ Bật App 1.1.1.1 để truy cập địa chỉ chính chủ Zo88.com

Signed Green

7 Aug 2026, 10:05 UTC50 viewsread 12 August 2026
Photo

⚡ AFF CUP BÙNG NỔ – AI SẼ NHẬN 100K TỪ ZO88? 🔥 🇻🇳 Việt Nam 🆚 Campuchia. ⏰ 20:00 | 07/08 | AFF Cup 2026 🎯 Dự đoán đúng tỷ số 🎁 Nhận ngay 100K từ ZO88 🔥 Tham gia ngay⚽️ Chốt kèo – Săn thưởng! 🏆 ZO88 OFFICIAL 📱@nhacaizo88 📱@zo88chinhhang ❤️❤ Bật App 1.1.1.1 để truy cập địa chỉ chính chủ Zo88.com

Signed Green

7 Aug 2026, 06:42 UTC53 viewsread 12 August 2026
Photo

🇻🇳 HLV KIM SANG-SIK ĐÁP TRẢ CỰC GẮT PHÁT NGÔN XEM NHẸ AFF CUP 🔥 HLV Kim Sang-sik khẳng định: Mọi giải đấu đều quan trọng. ⚽️ Sau chiến thắng 3-0 trước Indonesia, 🇻🇳 Việt Nam quyết tâm hạ Campuchia. 👆 Mục tiêu: Giữ vững ngôi đầu bảng A. 📲 Theo dõi AFF Cup 2026 cùng ZO88! 🏆 ZO88 OFFICIAL 📱@nhacaizo88 📱@zo88chinhhang ❤️❤ Bật App 1.1.1.1 để truy cập địa chỉ chính chủ Zo88.com

Signed Green

7 Aug 2026, 04:13 UTC52 viewsread 12 August 2026
Photo

🔥 SIÊU DỰ ĐOÁN AFF CUP – CHỐT TỶ SỐ, RINH 100K CÙNG ZO88! ⚽💰 🇻🇳 Việt Nam 🆚 Campuchia ⏰ 20:00 | 07/08 | AFF Cup 2026 🎯 Dự đoán đúng tỷ số 🎁 Nhận ngay 100K từ ZO88 ⚡ Tham gia ngay 🔥 Chớp cơ hội nhận thưởng! 🏆 ZO88 OFFICIAL 📱@nhacaizo88 📱@zo88chinhhang ❤️❤ Bật App 1.1.1.1 để truy cập địa chỉ chính chủ Zo88.com

Signed Green

6 Aug 2026, 12:07 UTC71 views1 reactionsread 12 August 2026
Photo

🔥 THÁI LAN CHẠM TAY VÀO BÁN KẾT AFF CUP 2026! 🇹🇭 🏷️ AFF Cup 2026 | Philippines 0-1 Thái Lan 🎯 Choolthong (85') ghi bàn, mang về 3 điểm quý giá 💥 Thái Lan toàn thắng 3 trận, giành 9 điểm tuyệt đối 🏆 ⚡ "Voi chiến" tiến sát tấm vé bán kết, phong độ đầy ấn tượng  🚀 Đồng hành cùng ZO88 để cập nhật AFF Cup 2026 mỗi ngày! 🔥 🏆 ZO88 OFFICIAL 📱@nhacaizo88 📱@zo88chinhhang ❤️❤ Bật App 1.1.1.1 để truy cập địa chỉ chính chủ Z

1

Signed Green

6 Aug 2026, 09:11 UTC69 views1 reactionsread 12 August 2026
Photo

🔥 LỊCH THI ĐẤU AFF CUP 2026 – LƯỢT CUỐI VÒNG BẢNG! ⚽️ 🏷️ AFF Cup 2026 | 20:00 | 07/08 👆 ⚽️ 🇻🇳 Việt Nam 🆚 🇰🇭 Campuchia | 🇸🇬 Singapore 🆚 🇮🇩 Indonesia 💥 Lượt đấu quyết định, cuộc đua vé bán kết cực kỳ kịch tính 🔥 Cập nhật diễn biến, theo dõi những màn so tài đến phút cuối 🚀 Đồng hành cùng ZO88 để hòa nhịp AFF Cup 2026 và đón xem các trận cầu đỉnh cao! ⚽️ 🏆 ZO88 OFFICIAL 📱@nhacaizo88 📱@zo88chinhhang ❤️❤ Bật App 1.1.

1

Signed Green

6 Aug 2026, 06:56 UTC429 viewsread 12 August 2026
Photo

⚽DỰ ĐOÁN ĐÚNG – TRÚNG 🌌🌌🌌🌌 - 🌌🌌🌌 - 🌌🌌🌌 💡Chạm niềm tin - nhận chiến thắng 🥰TIẾP LỬA CHIẾN BINH SAO VÀNG – CHINH PHỤC AFF CUP 2026 🥰 ⚔️ Việt Nam 🇻🇳 vs Campuchia ⏰ Thời gian dự đoán ⏳: đóng dự đoán trước trận 15 phút ✔️ Tham gia tại: https://t.me/zo88gamethuyeunuoc ✔ Có tài khoản ZO88 hợp lệ 🔐 ✍ Cú pháp dự đoán: UID trên game + 🏆 đội thắng + 🎯 tỷ số 📌 Ví dụ: 0386837 Việt Nam 2-1 (phiếu nạp gửi kèm vào group) Có tổ

Showing the 12 most recent of 22 posts we hold for @zo88chinhhang. 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.

Forward network

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.

Mentions

Named by 16 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“Z O 8 8 - Vô Là Thắng” (@zo88chinhhang), 5,004 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zo88chinhhang.

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.