Telegram RegisterThe public register of Telegram
Telegram profile photo for BOT MaxScalp

Channel

BOT MaxScalp

@AlertBotMaxScalp

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

3,141subscribers

-81 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-1001962915852
TypeChannel
Username@AlertBotMaxScalp
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/AlertBotMaxScalp

Growth

3,1413,2223,181.57 August 2026 — 3,222 subscribers7 August 2026 — 3,222 subscribers10 August 2026 — 3,208 subscribers14 August 2026 — 3,197 subscribers17 August 2026 — 3,184 subscribers21 August 2026 — 3,171 subscribers24 August 2026 — 3,163 subscribers27 August 2026 — 3,147 subscribers30 August 2026 — 3,141 subscribers7 August 202630 August 2026
9 measurements spanning 23 days, net -81. 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,129–3,234 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 09:373,141-6
27 Aug 2026, 13:233,147-16
24 Aug 2026, 09:083,163-8
21 Aug 2026, 00:423,171-13
17 Aug 2026, 16:293,184-13
14 Aug 2026, 08:083,197-11
10 Aug 2026, 19:153,208-14
7 Aug 2026, 10:013,222no change
7 Aug 2026, 09:583,222first reading

Engagement

20 posts held, back to 18 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 20 posts for this entry, the most recent from 4 September 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Jun 2025, 17:23 UTC197 viewsread 7 August 2026

BingX Futures, Bitget Futures #CELO/USDT All take-profit targets achieved 😎 Profit: 42.2535% 📈 Period: 3 Days 1 Hours 59 Minutes ⏰

20 Jun 2025, 17:22 UTC182 viewsread 7 August 2026

Binance Futures, Bitget Futures, ByBit USDT, OKX Futures #FLOW/USDT All take-profit targets achieved 😎 Profit: 40.6977% 📈 Period: 3 Days 2 Hours 10 Minutes ⏰

20 Jun 2025, 17:06 UTC154 viewsread 7 August 2026

Binance Futures, BingX Futures, Bitget Futures, ByBit USDT, HyperLiquid Futures(SOL/USDC), KuCoin Futures, OKX Futures #SOL/USDT All take-profit targets achieved 😎 Profit: 40.0787% 📈 Period: 3 Days 1 Hours 46 Minutes ⏰

20 Jun 2025, 09:58 UTC119 viewsread 7 August 2026

KuCoin Futures #CELO/USDT Take-Profit target 2 ✅ Profit: 20.6897% 📈 Period: 1 Days 9 Hours 34 Minutes ⏰

20 Jun 2025, 08:07 UTC104 viewsread 7 August 2026

Binance Futures, Bitget Futures, ByBit USDT, KuCoin Futures #ALICE/USDT Closed at stoploss after reaching take profit ⚠

19 Jun 2025, 14:47 UTC82 viewsread 7 August 2026

Binance Futures, BingX Futures, Bitget Futures, ByBit USDT, KuCoin Futures, OKX Futures #CELO/USDT Closed at stoploss after reaching take profit ⚠

19 Jun 2025, 12:49 UTC69 viewsread 7 August 2026

Binance Futures, BingX Futures, Bitget Futures, ByBit USDT, KuCoin Futures #GTC/USDT Stop Target Hit ⛔ Loss: 46.5116% 📉

19 Jun 2025, 06:10 UTC59 viewsread 7 August 2026

Binance Futures, BingX Futures, Bitget Futures, ByBit USDT, KuCoin Futures #GTC/USDT All entry targets achieved Average Entry Price: 0.2365 💵

19 Jun 2025, 00:45 UTC53 viewsread 7 August 2026

Binance Futures, BingX Futures, Bitget Futures, ByBit USDT, KuCoin Futures #GTC/USDT Entry 1 ✅ Average Entry Price: 0.2400 💵

19 Jun 2025, 00:45 UTC48 views0 reactionsread 7 August 2026

GTCUSDT, LONG, 4mARB5| Scalp, Entry: 0.24 - 0.233, Target 1:0.241608, Target 2: 0.243216, Target 3: 0.2448, Target 4: 0.2496, Trend-Line:0.233, Stop-Loss: 0.2314389, Leverage: Cross <<20.0x>>

19 Jun 2025, 00:26 UTC42 viewsread 7 August 2026

Binance Futures, BingX Futures, Bitget Futures, ByBit USDT, KuCoin Futures, OKX Futures #CELO/USDT Take-Profit target 1 ✅ Profit: 13.7931% 📈 Period: 8 Minutes ⏰

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

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

“BOT MaxScalp” (@AlertBotMaxScalp), 3,141 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/AlertBotMaxScalp.

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.