EPL lúc 22:30 VN: Fulham - Manchester United Carrick chịu áp lực lớn, MU cần thắng ở Craven Cottage khi Bruno đang là điểm tựa ghi bàn Kèo nhanh: MU là cửa trên nhưng áp lực tâm lý rất cao. Kèo MU -0.25 an toàn hơn -0.5; Fulham +0.5 có giá trị nếu đội hình MU thiếu Sesko/Shaw. Tham gia kênh bóng đá LC79: https://t.me/lc79_yeubongda

Channel
Yêu bóng đá
@lc79_yeubongda
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
44,778subscribers
-1,442 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002173450249 |
|---|---|
| Type | Channel |
| Username | @lc79_yeubongda |
| Description | 🎁 Nhận code tân thủ 79K: @lc79_code_bot 👉 CSKH: @Nhivtt_bot 👉 Link tải game: https://bancalc79.com 👉 Bot chơi game: https://t.me/laucuagame_PhnomPenh_bot 👉 Nhóm chính hãng: https://t.me/+XrFbTDkXZHFkMzY1 ⚠️ Lưu ý: CSKH không nhắn tin trước cho bất kỳ ai. |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/lc79_yeubongda |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 14:00 | 44,778 | -98 |
| 16 Sept 2026, 23:58 | 44,876 | -51 |
| 15 Sept 2026, 03:20 | 44,927 | -52 |
| 13 Sept 2026, 09:21 | 44,979 | -84 |
| 11 Sept 2026, 14:17 | 45,063 | -66 |
| 9 Sept 2026, 00:40 | 45,129 | -106 |
| 5 Sept 2026, 16:21 | 45,235 | -72 |
| 3 Sept 2026, 19:18 | 45,307 | -33 |
| 2 Sept 2026, 13:33 | 45,340 | -29 |
| 1 Sept 2026, 11:46 | 45,369 | -32 |
| 31 Aug 2026, 10:38 | 45,401 | -24 |
| 30 Aug 2026, 13:29 | 45,425 | -39 |
| 29 Aug 2026, 12:24 | 45,464 | -23 |
| 28 Aug 2026, 13:02 | 45,487 | -26 |
| 27 Aug 2026, 13:56 | 45,513 | -66 |
| 26 Aug 2026, 10:27 | 45,579 | -47 |
| 25 Aug 2026, 10:14 | 45,626 | -36 |
| 24 Aug 2026, 08:12 | 45,662 | -64 |
| 22 Aug 2026, 15:59 | 45,726 | -52 |
| 21 Aug 2026, 06:05 | 45,778 | first reading |
Engagement
178 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 90 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.1%
- avg views ÷ 44,778 subscribers
- Avg views / post
- 44.7
- 95 posts measured
- Reaction rate
- 1.18%
- reactions ÷ views · ER floor
- Posts in window
- 126
- of 178 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. It is computed over the 2 of 95 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 20 September 2026 |
|---|---|
| Posts held | 178 (3 August 2026 – 20 September 2026) |
| Views total | 4,244 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 09:27 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
- 833
- Videos
- 74
- Links
- 753
Lifetime counters from Telegram’s own channel header, read 23 September 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.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 4 of the 178 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 178 most recent posts we hold, published 3 August 2026 to 20 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.
Recent posts
Yêu bóng đá pinned a photo
EPL lúc 20:00 VN: Leeds United - Crystal Palace Leeds có form tốt và Calvert-Lewin vào nhịp, Palace mất Disasi vì treo giò Kèo nhanh: Leeds là cửa sáng theo 1X2 nhưng giá đã xuống khá sâu. Kèo Leeds -0.5 an toàn hơn -0.75 nếu Palace giữ được khối thấp. Tham gia kênh bóng đá LC79: https://t.me/lc79_yeubongda
EPL lúc 20:00 VN: Manchester City - Sunderland Man City toàn thắng, Haaland dẫn đầu vua phá lưới; Sunderland thiếu Reinildo và gặp bài test cực nặng Kèo nhanh: City là cửa thắng rõ nhất ngày. Kèo chấp sâu nên chỉ đẹp nếu đội hình đủ tốc độ biên và Haaland đá chính. Tham gia kênh bóng đá LC79: https://t.me/lc79_yeubongda
EPL lúc 20:00 VN: AFC Bournemouth - Liverpool Iraola trở lại Vitality cùng Liverpool, Bournemouth vẫn tìm chiến thắng đầu tiên tại EPL Kèo nhanh: Liverpool nhỉnh hơn nhờ chất lượng tuyến trên, nhưng giá 1X2 không quá sâu vì Bournemouth có điểm tựa sân nhà. Góc 10.5 nên đi thận trọng. Tham gia kênh bóng đá LC79: https://t.me/lc79_yeubongda
Yêu bóng đá pinned a photo
Atletico Madrid vs Real Madrid - Derby Madrid Derby Madrid vào khung giờ đẹp: Atletico có Metropolitano, Real có Mbappe - Bellingham - Vinicius để kéo nhịp tấn công. Thị trường đang nghiêng nhẹ về Real, nhưng đây là trận derby dễ đổi nhịp vì thẻ, góc và những pha tranh chấp giữa sân. Xem kèo như góc tham khảo, chờ XI thật trước giờ bóng lăn để đọc chắc hơn. #LC79 #LaLiga #AtleticoRealMadrid
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Lịch Ngoại hạng Anh từ 07:00 hôm nay đến 07:00 sáng mai (2026-09-20, giờ VN) • 20:00 - AFC Bournemouth vs Liverpool • 20:00 - Leeds United vs Crystal Palace • 20:00 - Manchester City vs Sunderland • 22:30 - Fulham vs Manchester United Bài lịch chi tiết: https://lc79.asia/2026/09/20/lich-ngoai-hang-anh-09-20-lc79/ Theo dõi lịch đấu, kèo và nhận định bóng đá cùng LC79: https://t.me/lc79_yeubongda
EPL lúc 23:30 VN: Nottingham Forest - Coventry City Forest gặp Coventry đang chưa có điểm và còn mất Awoniyi vì án treo giò Kèo nhanh: Forest sáng cửa thắng theo 1X2 trước Coventry thiếu đầu ra. Handicap -0.75 chỉ nên đi nhẹ vì Forest chưa bùng nổ bàn thắng sân nhà. Tham gia kênh bóng đá LC79: https://t.me/lc79_yeubongda
Showing the 12 most recent of 178 posts we hold for @lc79_yeubongda. 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 4 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.
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.
Declared links
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
https://bancalc79.com
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.
“Yêu bóng đá” (@lc79_yeubongda), 44,778 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/lc79_yeubongda.
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.