Sạp Hàng Bán Code - Kênh Thông Báo pinned a photo

Channel
Sạp Hàng Bán Code - Kênh Thông Báo
@saphangbancode
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
16,849subscribers
-2,475 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003867622253 |
|---|---|
| Type | Channel |
| Username | @saphangbancode |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 56 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/saphangbancode |
Topic
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 90% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 14:18 | 16,849 | -4 |
| 3 Nov 2026, 17:11 | 16,853 | -20 |
| 2 Nov 2026, 20:01 | 16,873 | -2 |
| 1 Nov 2026, 19:28 | 16,875 | -10 |
| 31 Oct 2026, 15:56 | 16,885 | -14 |
| 30 Oct 2026, 14:09 | 16,899 | -18 |
| 29 Oct 2026, 15:44 | 16,917 | -11 |
| 28 Oct 2026, 15:17 | 16,928 | -12 |
| 27 Oct 2026, 13:30 | 16,940 | -16 |
| 26 Oct 2026, 16:28 | 16,956 | -31 |
| 25 Oct 2026, 16:27 | 16,987 | -14 |
| 24 Oct 2026, 16:54 | 17,001 | -13 |
| 23 Oct 2026, 15:36 | 17,014 | -28 |
| 22 Oct 2026, 13:19 | 17,042 | -23 |
| 21 Oct 2026, 06:00 | 17,065 | -15 |
| 20 Oct 2026, 01:09 | 17,080 | -20 |
| 18 Oct 2026, 23:36 | 17,100 | -11 |
| 17 Oct 2026, 21:16 | 17,111 | -27 |
| 16 Oct 2026, 23:29 | 17,138 | -27 |
| 16 Oct 2026, 00:35 | 17,165 | first reading |
Engagement
184 posts held, back to 3 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 57 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.681%
- avg views ÷ 16,849 subscribers
- Avg views / post
- 115
- 15 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 30
- of 184 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.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 184 (3 August 2026 – 4 November 2026) |
| Views total | 1,722 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 16:03 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
- 637
- Videos
- 344
- Links
- 855
Lifetime counters from Telegram’s own channel header, read 4 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 13m 01s
- Average length
- 28s
Measured directly from 28 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
813 reactions across 55 posts, in 6 distinct kinds. The most used accounts for 96.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 788 | 96.9% | |
| 🥰 | 11 | 1.35% | |
| 🔥 | 8 | 0.984% | |
| 👎 | 3 | 0.369% | |
| 👍 | 2 | 0.246% | |
| 😁 | 1 | 0.123% |
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 55 of the 184 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 813 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 184 most recent posts we hold, published 3 August 2026 to 4 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: 0 of 30 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).
🎁💰 TÍC TẮC - TÍCH LŨY VỚI ĐẠI TIỆC KHUYẾN MÃI TIC 🎁💰 ✨ Nạp đầu +100%, nhân vốn tối đa tới 20 TRIỆU ✨ Hoàn trả đến 1.4%, vốn về liên tục ✨ Săn hũ & sự kiện thể thao đến hàng trăm triệu mỗi ngày 👇 Săn thưởng ngay: https://choitic88.world/choi-ngay-01 🤩TIC88 - CÓ TIC CÓ TIỀN🤩
Sạp Hàng Bán Code - Kênh Thông Báo pinned a photo
👌👌👌👌👌👌👌 🔤9️⃣🔤🔤🔤 🫧🫧🫧🫧 🫧🫧🫧🫧 🤩🤩🤩🤩🤩🤩🤩🤩🤩 🫧🫧🫧🫧 🫧🫧🫧🫧 ✅ Phần thưởng vượt cấp NỔ HŨ đặt cược càng nhiều phần thưởng càng lớn ✅ Nhanh tay đăng nhập i9BET để nhận thưởng ❗️ ✅ Tiền thưởng cao nhất lên đến 141,687.000 VND❗️ ✅ Thời gian phát thưởng vào 13h hàng ngày❗️ ✅ Mọi thắc mắc quý khách vui lòng liên hệ CSKH trực tuyến để được hỗ trợ ạ. ✅ i9BET ❤️LẤY UY TÍN ĐẶT LÊN HÀNG ĐẦU👍 NƠI XỨNG ĐÁNG ĐỂ BẠN ĐẶT TRỌN NIỀM TIN…
Sạp Hàng Bán Code - Kênh Thông Báo pinned a video
⚡ NHÀ CÁI TỐC ĐỘ TIC88 ⚡ NẠP RÚT 5 PHÚT – TRỄ 1 PHÚT, ĐỀN 1 TRIỆU!!! Chờ đợi tiền về làm gián đoạn cuộc vui? 🥴 Gia nhập TIC88, nơi mọi giao dịch được cam kết chuẩn hóa, tốc độ và sòng phẳng tuyệt đối. ⏰ Nạp rút tốc độ trong tối đa 5 PHÚT ✅ CAM KẾT: Trễ 1 PHÚT, đền 1 TRIỆU, cộng trực tiếp vào tài khoản 📈 Trải nghiệm tốc độ nạp rút “”bá đạo”” nhất thị trường ngay hôm nay: Tại đây 🍀
Sạp Hàng Bán Code - Kênh Thông Báo pinned a photo
🎁💰 TÍC TẮC - TÍCH LŨY VỚI ĐẠI TIỆC KHUYẾN MÃI TIC 🎁💰 ✨ Nạp đầu +100%, nhân vốn tối đa tới 20 TRIỆU ✨ Hoàn trả đến 1.4%, vốn về liên tục ✨ Săn hũ & sự kiện thể thao đến hàng trăm triệu mỗi ngày 👇 Săn thưởng ngay: https://choitic88.world/choi-ngay-01 🤩TIC88 - CÓ TIC CÓ TIỀN🤩
Sạp Hàng Bán Code - Kênh Thông Báo pinned a video
🧂⚽️🏀🏈⚾️🥎🎾🏐🏀🏈⚾️🥎🎾 🫧🫧🫧🫧 🫧🫧🫧🫧 🤩🤩🤩🤩🤩🤩🤩🤩🤩 🫧🫧🫧🫧 🫧🫧🫧🫧 😋 GIÚP ĐỠ CÔ MIỀN TRUNG XA QUÊ, VÀO SÀI GÒN BÁN CHỔI MƯU SINH, CHẮT CHIU TỪNG ĐỒNG LO CHO GIA ĐÌNH. 🆗 ✅ Cô từ miền Trung vào Sài Gòn mưu sinh bằng nghề bán chổi. ❤️ ✅ Ngày ngày rong ruổi khắp phố phường, ❤️ ✅ Chắt chiu từng đồng lo cho gia đình.❤️ ✅ Cuộc sống còn nhiều vất vả, khó khăn,❤️ ✅ Nhưng cô vẫn miệt mài chẳng ngại nắng mưa.❤️ ✅ Mong rằng những sự sẻ c…
Sạp Hàng Bán Code - Kênh Thông Báo pinned a video
⚡ NHÀ CÁI TỐC ĐỘ TIC88 ⚡ NẠP RÚT 5 PHÚT – TRỄ 1 PHÚT, ĐỀN 1 TRIỆU!!! Chờ đợi tiền về làm gián đoạn cuộc vui? 🥴 Gia nhập TIC88, nơi mọi giao dịch được cam kết chuẩn hóa, tốc độ và sòng phẳng tuyệt đối. ⏰ Nạp rút tốc độ trong tối đa 5 PHÚT ✅ CAM KẾT: Trễ 1 PHÚT, đền 1 TRIỆU, cộng trực tiếp vào tài khoản 📈 Trải nghiệm tốc độ nạp rút “”bá đạo”” nhất thị trường ngay hôm nay: Tại đây 🍀
Showing the 12 most recent of 184 posts we hold for @saphangbancode. 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.
Mentions
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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Sạp Hàng Bán Code - Kênh Thông Báo” (@saphangbancode), 16,849 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/saphangbancode.
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.