今晚咁多野玩😁 淨係睇岩喱兩場😁 繼續過關過關再過關😁 #足球事前 #金仔心水
🔥38custom 60643899181031834736custom 62826549849452748014❤3custom 63255743740908693713custom 60869756693491257252custom 60623694495230274611

Channel
@kamkei8
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
10,970subscribers
+306 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003797956847 |
|---|---|
| Type | Channel |
| Username | @kamkei8 |
| 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 | 19 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/kamkei8 |
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 11 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 |
|---|---|---|
| 19 Sept 2026, 16:17 | 10,970 | +38 |
| 17 Sept 2026, 03:19 | 10,932 | +11 |
| 15 Sept 2026, 02:57 | 10,921 | +6 |
| 13 Sept 2026, 15:20 | 10,915 | -7 |
| 11 Sept 2026, 21:19 | 10,922 | +80 |
| 9 Sept 2026, 10:41 | 10,842 | +13 |
| 6 Sept 2026, 05:20 | 10,829 | +11 |
| 3 Sept 2026, 21:17 | 10,818 | +9 |
| 2 Sept 2026, 10:45 | 10,809 | +9 |
| 1 Sept 2026, 10:17 | 10,800 | +26 |
| 30 Aug 2026, 07:44 | 10,774 | -1 |
| 29 Aug 2026, 04:07 | 10,775 | +5 |
| 28 Aug 2026, 03:34 | 10,770 | +27 |
| 27 Aug 2026, 03:55 | 10,743 | +27 |
| 26 Aug 2026, 06:33 | 10,716 | +2 |
| 25 Aug 2026, 04:08 | 10,714 | +3 |
| 22 Aug 2026, 06:06 | 10,711 | +3 |
| 20 Aug 2026, 18:45 | 10,708 | +7 |
| 19 Aug 2026, 15:53 | 10,701 | -2 |
| 18 Aug 2026, 16:57 | 10,703 | first reading |
136 posts held, back to 4 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 38 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.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 136 (4 August 2026 – 1 September 2026) |
| Views total | 57,520 |
| Reactions total | 1,027 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 20:10 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.
Measured directly from 12 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.
3,547 reactions across 134 posts, in 11 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,064 | 30.0% | |
| 🔥 | 1,027 | 29.0% | |
| custom 6325574374090869371 | 571 | 16.1% | |
| custom 6064389918103183473 | 315 | 8.88% | |
| custom 6086975669349125725 | 189 | 5.33% | |
| custom 6282654984945274801 | 165 | 4.65% | |
| custom 6265055196808743656 | 107 | 3.02% | |
| custom 6062369449523027461 | 55 | 1.55% | |
| custom 6309978677824196525 | 46 | 1.30% | |
| custom 6064622658085985400 | 7 | 0.197% | |
| custom 6309575058272554305 | 1 | 0.028% |
Custom emoji. 9 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 134 of the 136 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 3,547 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 136 most recent posts we hold, published 4 August 2026 to 1 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kamkei8. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 136 most recent posts we hold for this entry, published 4 August 2026 to 1 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
今晚咁多野玩😁 淨係睇岩喱兩場😁 繼續過關過關再過關😁 #足球事前 #金仔心水
🔥38custom 60643899181031834736custom 62826549849452748014❤3custom 63255743740908693713custom 60869756693491257252custom 60623694495230274611
😁金仔X易博 估波膽活動😁 估中波膽派88(限20名)😁 😁開始時間:(開場前截止) 😁玩法:喺呢度下面留言波膽 記得喺呢個post下面留言波膽 (重複留言不計)(編輯留言不計) 最先估中20名有獎 😁明天會派發落易博帳號 未開帳號的立即註冊😁😁 😁 www.eb8hk.com 😁 www.eb8hk.com 有咩唔明😁😁😁 隨時搵金仔 @eb8hkc 😁
❤12custom 60643899181031834735custom 63099786778241965252
一打開個馬會又收錢😁😁😁 正氣巴塞冇得頂😁😁😁 好撚醉,訓多陣先😁😁😁
❤31🔥12custom 63255743740908693717custom 60643899181031834732
金仔在九龍城醉了😂🕺
❤17custom 62826549849452748017🔥4
嬲嬲地,搞下同場過關😁
🔥23❤8custom 63255743740908693715
出師不利,飲啖酒下口😁
❤15custom 60643899181031834737🔥3custom 62826549849452748012
星期一😁 第一擊😁 敘利亞U20 對 印度U20😁 2.5入球😁😁😁大波無誤!
🔥31❤9custom 60623694495230274612custom 63099786778241965252
😁金仔提提大家!😁 馬會會員積分將於 今日2026年8月31日到期, 大家快D換領獎品!😁
❤12custom 60643899181031834734🔥2
岩岩番到香港😁😁😁 話左今星期唔賭了😁😁 今星期跟足我既手足們😁 平注實收3.431倍😁 唔好再問金仔咁多2皮去片😁 大家繼續一齊日日贏馬會😁
custom 606438991810318347328❤10custom 60623694495230274617
我要賭牌🤣 抽大細 海底撈真係多花臣😁😁
🔥10custom 60643899181031834733custom 62826549849452748012❤1
財神到財神到好心得好報🔥 係大陸真係樂而忘返😁 不過聽日返黎!大家等我😁 😁😁😁😁😁😁 😁😁😁😁😁😁 😁😁😁😁😁😁 😁😁😁😁😁😁
🔥36❤12custom 60643899181031834734custom 62826549849452748011
訓醒見到PSG搞野😁 果種心情真係難以形容😁 繼續渡假🏖️ 明天總結
custom 606438991810318347323🔥6❤4custom 60869756693491257251
Showing the 12 most recent of 136 posts we hold for @kamkei8. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“金仔🫂 波馬心水頻道💰” (@kamkei8), 10,970 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/kamkei8.
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.