Telegram RegisterThe public register of Telegram
Telegram profile photo for BXO TRADING - LEARN

Channel

BXO TRADING - LEARN

@BXOTrading

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

3,036subscribers

-74 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002288609417
TypeChannel
Username@BXOTrading
Created18 March 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live28 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/BXOTrading

Growth

3,0363,1103,0737 August 2026 — 3,110 subscribers7 August 2026 — 3,110 subscribers10 August 2026 — 3,096 subscribers13 August 2026 — 3,083 subscribers16 August 2026 — 3,071 subscribers20 August 2026 — 3,059 subscribers23 August 2026 — 3,048 subscribers26 August 2026 — 3,043 subscribers28 August 2026 — 3,036 subscribers7 August 202628 August 2026
9 measurements spanning 21 days, net -74. 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 3,025–3,121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 15:553,036-7
26 Aug 2026, 00:163,043-5
23 Aug 2026, 03:523,048-11
20 Aug 2026, 01:033,059-12
16 Aug 2026, 21:473,071-12
13 Aug 2026, 17:383,083-13
10 Aug 2026, 22:233,096-14
7 Aug 2026, 18:333,110no change
7 Aug 2026, 18:233,110first reading

Engagement

7 posts held, back to 18 March 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 16 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

40 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2050.0%
🙏615.0%
🤝615.0%
👏410.0%
👌25.00%
💯25.00%

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 5 of the 7 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 40reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 18 March 2025 to 16 February 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

16 Feb 2026, 16:16 UTC708 views10 reactionsread 7 August 2026
Photo

HOW TO IDENTIFY MARKET MANIPULATION: 🕯 When You See This Chart Look This Rejections That Means There Is Manipulation There Is Lots of Chance Your Trade Fail In Last Few Seconds. Always Try To Avoid This Types of Charts For Binary Trading.

👍6🤝4

6 Feb 2026, 17:00 UTC824 views8 reactionsread 7 August 2026
Photo

Bearish Engulfing: Double Candlestick Pattern (Indicate Strong Selling).

🙏6💯2

6 Feb 2026, 16:52 UTC835 views7 reactionsread 7 August 2026
Photo

Bullish Engulfing: Double Candlestick Pattern (Indicate Strong Buying).

👍5👌2

5 Feb 2026, 20:53 UTC882 views6 reactionsread 7 August 2026
Photo

Spinning Top: Single Candlestick Pattern.

👍6

5 Feb 2026, 18:12 UTC779 views9 reactionsread 7 August 2026

Guys, i inform you one important thing we never send you message first, we deal with only this account: @bxotrader and this is our official account. Otherwise all accounts fake or scam don't trust anyone don't give your money to anyone 👎 If you giving your money to anyone it's your own risk i am not responsible for anything.

👏4👍3🤝2

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

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

“BXO TRADING - LEARN” (@BXOTrading), 3,036 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/BXOTrading.

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.