Telegram RegisterThe public register of Telegram

Channel

Kingslayer DCA Bo.Botfx

@BoBotfx_Kingslayer_DCA

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

189subscribers

+5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002484996057
TypeChannel
Username@BoBotfx_Kingslayer_DCA
DescriptionMT5 Kingslayer DCA 20.07.26 10k VantageMarkets-Live 11 33860634 BoBotfx#1
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
On Telegramt.me/BoBotfx_Kingslayer_DCA

Growth

184189186.57 Aug 2026, 13:33 — 184 subscribers8 Aug 2026, 04:53 — 189 subscribers8 Aug 2026, 12:03 — 189 subscribers7 Aug 2026, 13:338 Aug 2026, 12:03
3 measurements taken within a single day, net +5. 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 183–190 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:03189no change
8 Aug 2026, 04:53189+5
7 Aug 2026, 13:33184first reading

Engagement

20 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
22.6%
avg views ÷ 189 subscribers
Avg views / post
42.8
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (7 August 20267 August 2026)
Views total856
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12: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
102
Links
2

Lifetime counters from Telegram’s own channel header, read 8 August 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.

Recent posts

7 Aug 2026, 17:31 UTC45 viewsread 8 August 2026
Photo

Symbol: XAUUSD (M30) @ Server Time: 2026.08.07 20:31:06

7 Aug 2026, 17:31 UTC45 viewsread 8 August 2026

💱 Symbol: XAUUSD 📉 Signal: Buy 💠 Entry: 4339.65 🔷 Takeprofit: 4358.40 🎲 Confidence level: 82.8% ═════════════ 🤖 Kingslayer Deepseek 📬©Bo.Botfx | @nguyenvanbo128

7 Aug 2026, 17:31 UTC45 viewsread 8 August 2026

Vàng vừa làm trò 'quét stop' kinh điển: chọc thủng vùng 4329 để hốt hết lệnh bán yếu, rồi đóng nến bên trên 4339 – nghe như một cú lừa ngoạn mục của phe mua. Xu hướng chung vẫn đang lên, mình thấy đây là vùng săn lệnh long đẹp, giá đứng vững trên 4327 thì phe bán coi như bó tay. Mục tiêu không xa đâu, cứ để giá chạy lên vùng 4358, nơi có thanh khoản mua đang chờ. ═════════════ 🤖 Kingslayer Deepseek 📬©Bo.Botfx | @nguy

7 Aug 2026, 17:29 UTC41 viewsread 8 August 2026

🛡️ Đóng toàn bộ lệnh 💰 Profit: 46.20 🧠 Lệnh đầu tiên âm tới 27 đô, nghe muốn xé màn hình, nhưng DCA đã biết cách vùng lên: gom thêm ở vùng giá thấp hơn rồi bứt phá. Kết quả cuối cùng dương 46 đô – không phải quá đã nhưng đủ để thấy chiến thuật trung bình giá đã phát huy tác dụng. Đây là kiểu 'thua keo này bày keo khác', miễn là quản lý vốn tốt và kiên nhẫn chờ đợi, thì cú lội ngược dòng vẫn nằm trong tầm tay. ══════

7 Aug 2026, 17:01 UTC40 viewsread 8 August 2026

⚡ Lots DCA: 0.05 🚀 Entry: 4329.40 🎯 TP Price: 4342.00 📊 Support/Resistance: 4328.60 ═════════════ 🤖 Kingslayer Deepseek 📬©Bo.Botfx | @nguyenvanbo128

7 Aug 2026, 17:01 UTC41 viewsread 8 August 2026

Giá đang rơi đúng vào vùng hỗ trợ quanh 4328-4330, hội tụ Fibonacci 61.8% của nhịp tăng từ 4302 lên 4372 và vùng breakout trước đó – chỗ này mà không mua thì tiếc thật sự. Lệnh đang âm khoảng 115 đô, nhưng thêm 0.05 lot là kéo giá trung bình xuống dưới 4339, chỉ cần hồi lên 4342 là cả lệnh xanh trở lại. Không cần phải nơm nớp hay cầu trời, cứ nhẹ nhàng vô, chờ nó quay lại là xong. ═════════════ 🤖 Kingslayer Deepseek

7 Aug 2026, 16:00 UTC41 viewsread 8 August 2026

⚡ Lots DCA: 0.05 🚀 Entry: 4341.35 🎯 TP Price: 4352.21 📊 Support/Resistance: 4340.00 ═════════════ 🤖 Kingslayer Deepseek 📬©Bo.Botfx | @nguyenvanbo128

7 Aug 2026, 16:00 UTC37 viewsread 8 August 2026

Vàng đang hồi về vùng 4340 - nơi mà nó đã test mấy lần trong phiên và bật lại, kiểu như cái ghế sofa cũ kỹ nhưng vẫn đỡ được mông vậy. Lệnh BUY cũ đang âm nhẹ, chưa có gì phải hoảng, vì phía dưới còn dải hỗ trợ 4339-4340 và Fibonacci 61.8% quanh 4328. Thêm một lệnh 0.05 lots ở đây để kéo giá hòa vốn về quanh 4352, chỉ cần vàng hồi nhẹ là cả cụm có lời, mục tiêu lời khoảng 0.5% tài khoản, không tham lam. Nếu lỡ nó phá

7 Aug 2026, 15:30 UTC38 viewsread 8 August 2026

💱 Symbol: XAUUSD 📉 Signal: Buy 💠 Entry: 4351.52 🔷 Takeprofit: 4371.77 🎲 Confidence level: 82.0% ═════════════ 🤖 Kingslayer Deepseek 📬©Bo.Botfx | @nguyenvanbo128

7 Aug 2026, 15:30 UTC37 viewsread 8 August 2026
Photo

Symbol: XAUUSD (M30) @ Server Time: 2026.08.07 18:30:53

7 Aug 2026, 15:30 UTC36 viewsread 8 August 2026

Xu hướng hiện tại vẫn là một con sóng tăng mạnh, từ vùng 4080 bật lên 4371 rồi hồi về 4340 – khu vực có ba lần chạm đáy, cho thấy bên mua đã 'đóng cọc' ở vùng này. Cây nến M30 vừa đóng là một cây tăng nuốt gọn nến giảm, tín hiệu đảo chiều khá rõ. Mình sẽ ưu tiên vào lệnh mua theo xu hướng chính, đặt mục tiêu về đỉnh cũ 4371, nhưng phải canh cắt lỗ dưới vùng hỗ trợ 4340 nếu tình hình xấu. ═════════════ 🤖 Kingslayer De

7 Aug 2026, 15:09 UTC38 viewsread 8 August 2026

🛡️ Đóng toàn bộ lệnh 💰 Profit: 14.46 🧠 Chốt lời là xong, nhưng chuỗi DCA này đúng kiểu 'cười ra nước mắt'. Lệnh đầu tiên âm tới $25, tưởng thua to, ai ngờ lệnh thứ hai với lot lớn hơn ăn tới $39, kéo cả series lên dương $14.46. Nhìn chung là có lãi, nhưng mức lãi mỏng manh như sợi tóc. DCA mà cứu được lệnh lỗ thì cũng đáng mặt, nhưng phải thừa nhận là may hơn khôn. Lần sau thấy lệnh đầu lỗ sâu quá, phải tính lại liề

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

Citation-graph rank

Citation-graph rank — 710,288 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Kingslayer DCA Bo.Botfx” (@BoBotfx_Kingslayer_DCA), 189 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/BoBotfx_Kingslayer_DCA.

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.