Channel
@code8kbot
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
539subscribers
+411 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002299498140 |
|---|---|
| Type | Channel |
| Username | @code8kbot |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/code8kbot |
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 21 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 11:38 | 539 | -8 |
| 6 Sept 2026, 14:01 | 547 | +68 |
| 30 Aug 2026, 00:43 | 479 | +148 |
| 22 Aug 2026, 21:47 | 331 | +193 |
| 15 Aug 2026, 10:14 | 138 | +10 |
| 14 Aug 2026, 21:16 | 128 | first reading |
12 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 1 page 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 12 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.
12 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 75.0% | |
| 🔥 | 3 | 25.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 6 of the 12 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 11 August 2026 to 14 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.
DANH SÁCH EVENT CODE 8KBET NGÀY 14/8 TIME DONE TỪ 24H-48H taolafang255 vigiahien Umum125 Nex Thonglap23 Hilolong Binhphat886 Minhoppa quangdaver Tuantu009009 Moitaigame Kentd6789 P1022009 quocphuh2k rongdenfunlua Phutrongzz mytom02 longka123999 X893240 Phunho95 ❌CHÚ Ý: KHÔNG HỖ TRỢ MUA LẠI KHI TK LỖI HOẶC K ĐỦ ĐIỀU
❤5
BET8KBET - Minhoppa - Nhập thành công: 18 Chỉ giải quyết khiếu nại trong 24h kể từ lúc trả kết quả BET8KBET - bolatienphong - Nhập thành công: 28 Chỉ giải quyết khiếu nại trong 24h kể từ lúc trả kết quả BET8KBET - Tuantu009009 - Nhập thành công: 28 Chỉ giải quyết khiếu nại trong 24h kể từ lúc trả kết quả BET8KBET - thachdbne11 - Nhập thành công: 38 Chỉ giải quyết khiếu nại trong 24h kể từ lúc trả kết quả BET8KBET…
⚠️ Tài khoản đã bị gỡ 🎮 Game: 8KBET 👤 Tài khoản: hayen20100 🎟️ Code: bE2C5IB8 📩 Phản hồi: Tài khoản sai hoặc không phù hợp để nhận thưởng ✅ Nhập code thành công! 🎮 Game: 8KBET 👤 Tài khoản: ductri57 🎟️ Code: f6D4qm6W 📩 Phản hồi: {"code":200,"message":"38"} ✅ Nhập code thành công! 🎮 Game: 8KBET 👤 Tài khoản: Quayy79 🎟️ Code: DstGfvq8 📩 Phản hồi: {"code":200,"message":"18"} ✅ Nhập code thành công! 🎮 Game: 8KBET 👤 …
❤1
DANH SÁCH EVENT CODE 8KBET NGÀY 13/8 TIME DONE TỪ 24H-48H ❌CHÚ Ý: KHÔNG HỖ TRỢ MUA LẠI KHI TK LỖI HOẶC K ĐỦ ĐIỀU KIỆN Quayy79 hayen20100 Thonglap23 ductri57 Vantruong99pp phucthinh27 Utem77g1 huyentrang63 Phutrongzz P1022009
✅ Nhập code thành công! 🎮 Game: 8KBET 👤 Tài khoản: chunhyttt 🎟️ Code: DfaZZXQ8 📩 Phản hồi: {"code":200,"message":"18"} ⚠️ Tài khoản đã bị gỡ 🎮 Game: 8KBET 👤 Tài khoản: taolafang255 🎟️ Code: P5JEe1st 📩 Phản hồi: Đã tham gia cùng ngày vui lòng không nhận lại!! ✅ Nhập code thành công! 🎮 Game: 8KBET 👤 Tài khoản: phamminhhao123 🎟️ Code: P5JEe1st 📩 Phản hồi: {"code":200,"message":"38"}
DONE, CÓ TÊN VÔ CHECK ✅ Nhập code thành công! 🎮 Game: 8KBET 👤 Tài khoản: Tuantu009009 🎟️ Code: yluxqIIT 📩 Phản hồi: {"code":200,"message":"18"} ✅ Nhập code thành công! 🎮 Game: 8KBET 👤 Tài khoản: Quayy79 🎟️ Code: 6k8zxgwr 📩 Phản hồi: {"code":200,"message":"18"} ✅ Nhập code thành công! 🎮 Game: 8KBET 👤 Tài khoản: bolatienphong 🎟️ Code: YBiv7i63 📩 Phản hồi: {"code":200,"message":"28"} ✅ Nhập code thành công! 🎮 Gam…
❤1
DANH SÁCH EVENT CODE 8KBET NGÀY 12/8 TIME DONE TỪ 24H-48H ❌CHÚ Ý: KHÔNG HỖ TRỢ MUA LẠI KHI TK LỖI HOẶC K ĐỦ ĐIỀU KIỆN bu09 Minhoppa chunhyttt blackjoe Moitaigame phamminhhao123 khangcanh2008 qtruongoccho Nit1133
❤2
DANH SÁCH NHẬN CODE LIVE SC88 NGÀY 12/8 p102****|Trong123 huudu****|Duong2009 Tuan****9|Tuantu1230909 fan***|Mm123123
DANH SÁCH EVENT CODE F8BET NGÀY 11/8 Tuantu009009 ductri57 lenaok8386 Minhoppa
DANH SÁCH EVENT CODE NGÀY 10/8 Minhoppa Vipleotop123 Linhbg33 toantxts Tuantu009009 Quayy79 Tayok1991 thachdbne11 bolatienphong taolafang255
🔥3
KÊNH THÔNG BÁO CODE 8KBET pinned «😘😗😙😋😛 KÊNH CẬP NHẬT DANH SÁCH TRÚNG EV CODE ⚡️𝐊𝐇𝐔𝐘Ế𝐍 𝐌Ã𝐈 𝐆𝐀𝐌𝐄 𝐍𝐄𝐖𝐬 https://t.me/freeeatmoney 🟡𝐓𝐄𝐀𝐌 𝐗𝐎𝐌 𝐋Á https://t.me/xom_nhala»
😘😗😙😋😛 KÊNH CẬP NHẬT DANH SÁCH TRÚNG EV CODE ⚡️𝐊𝐇𝐔𝐘Ế𝐍 𝐌Ã𝐈 𝐆𝐀𝐌𝐄 𝐍𝐄𝐖𝐬 https://t.me/freeeatmoney 🟡𝐓𝐄𝐀𝐌 𝐗𝐎𝐌 𝐋Á https://t.me/xom_nhala
Showing the 12 most recent of 12 posts we hold for @code8kbot. 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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“KÊNH THÔNG BÁO CODE 8KBET” (@code8kbot), 539 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/code8kbot.
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.