Channel
@MarginScalpsPRO
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
3,719subscribers
-321 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001167037038 |
|---|---|
| Type | Channel |
| Username | @MarginScalpsPRO |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/MarginScalpsPRO |
Crypto & trading — 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 14 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 07:50 | 3,719 | -3 |
| 2 Nov 2026, 02:41 | 3,722 | -12 |
| 30 Oct 2026, 10:16 | 3,734 | -73 |
| 27 Oct 2026, 12:46 | 3,807 | -58 |
| 24 Oct 2026, 05:18 | 3,865 | -57 |
| 21 Oct 2026, 15:36 | 3,922 | -20 |
| 18 Oct 2026, 12:06 | 3,942 | -9 |
| 15 Oct 2026, 20:25 | 3,951 | -9 |
| 12 Oct 2026, 18:28 | 3,960 | -3 |
| 6 Oct 2026, 03:59 | 3,963 | -9 |
| 28 Sept 2026, 20:21 | 3,972 | -16 |
| 18 Sept 2026, 21:57 | 3,988 | -3 |
| 14 Sept 2026, 13:15 | 3,991 | -5 |
| 11 Sept 2026, 10:16 | 3,996 | -8 |
| 6 Sept 2026, 20:18 | 4,004 | -5 |
| 2 Sept 2026, 10:56 | 4,009 | -3 |
| 30 Aug 2026, 04:45 | 4,012 | -3 |
| 27 Aug 2026, 10:08 | 4,015 | -4 |
| 24 Aug 2026, 19:04 | 4,019 | -1 |
| 18 Aug 2026, 19:56 | 4,020 | first reading |
20 posts held, back to 7 June 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pages of 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 11 June 2025. An engagement rate over an empty window would be a number about nothing.
PAIR: KAVAUSDT TYPE: SHORT LEVERAGE: Cross 20x Entry Targets: 1) 0.4415 2) 0.4592 (DCA) Take-Profit Targets: 0.4393 - 0.4358 - 0.4305 - 0.4238 - 0.415 - 0.4062 - 0.3929 - 0.3709 Stoploss: 0.468 @MarginScalpsPRO
PAIR: APEUSDT TYPE: SHORT LEVERAGE: Cross 20x Entry Targets: 1) 0.7248 2) 0.7538 (DCA) Take-Profit Targets: 0.7212 - 0.7176 - 0.7139 - 0.7031 - 0.6958 - 0.6813 - 0.6596 - 0.6161 Stoploss: 0.7683 @MarginScalpsPRO
Margin Scalps PRO pinned a photo
⚡️ Trade, win, repeat ‼️ Join the Bybit Trade Masters Grand Prix 2025 and let’s make some serious moves. Don’t miss out! 🚀 Bybit $1.5M derivatives trading competition happening now! 🌟 Highlights: 📈 1.5 million USDT prize pool based on trading volume and profits 🎉 Top 3 traders invited to exclusive VIP Gala 2025 🎟 Earn lucky draw tickets daily—up to 3 per day—with USDT giveaways 🎁 Become VIP by completing $5M deri…
PAIR: LDOUSDT TYPE: SHORT LEVERAGE: Cross 20x Entry Targets: 1) 0.805 2) 0.8533 (DCA) Take-Profit Targets: 0.7994 - 0.7945 - 0.7849 - 0.7728 - 0.7567 - 0.7406 - 0.7165 - 0.6762 Stoploss: 0.8855 @MarginScalpsPRO
PAIR: SANDUSDT TYPE: SHORT LEVERAGE: Cross 20x Entry Targets: 1) 0.2749 2) 0.2859 (DCA) Take-Profit Targets: 0.2735 - 0.2722 - 0.2708 - 0.2667 - 0.2639 - 0.2584 - 0.2502 - 0.2337 Stoploss: 0.2914 @MarginScalpsPRO
PAIR: MASKUSDT TYPE: SHORT LEVERAGE: Cross 20x Entry Targets: 1) 1.672 2) 1.7556 (DCA) Take-Profit Targets: 1.6602999999999999 - 1.6503 - 1.6301999999999999 - 1.6051 - 1.5716999999999999 - 1.5382 - 1.4881 - 1.4045 Stoploss: 1.7890000000000001 @MarginScalpsPRO
PAIR: AVAXUSDT TYPE: LONG LEVERAGE: Cross 20x Entry Targets: 1) 20.93 2) 20.0928 (DCA) Take-Profit Targets: 21.0765 - 21.2021 - 21.4533 - 21.7672 - 22.1858 - 22.6044 - 23.2323 - 24.2788 Stoploss: 19.6742 @MarginScalpsPRO
PAIR: BTCUSDT TYPE: LONG LEVERAGE: Cross 20x Entry Targets: 1) 105734 2) 100447.3 (DCA) Take-Profit Targets: 106474.138 - 107108.542 - 108377.35 - 109963.36 - 112078.04 - 114192.72 - 117364.74 - 122651.44 Stoploss: 97275.28 @MarginScalpsPRO
PAIR: LDOUSDT TYPE: LONG LEVERAGE: Cross 20x Entry Targets: 1) 0.82 2) 0.7708 (DCA) Take-Profit Targets: 0.8257 - 0.8307 - 0.8405 - 0.8528 - 0.8692 - 0.8856 - 0.9102 - 0.9512 Stoploss: 0.738 @MarginScalpsPRO
PAIR: CHZUSDT TYPE: LONG LEVERAGE: Cross 20x Entry Targets: 1) 0.03855 2) 0.037 (DCA) Take-Profit Targets: 0.0387 - 0.0389 - 0.0391 - 0.0397 - 0.0401 - 0.0409 - 0.042 - 0.0443 Stoploss: 0.0359 @MarginScalpsPRO
PAIR: SANDUSDT TYPE: LONG LEVERAGE: Cross 20x Entry Targets: 1) 0.2807 2) 0.2695 (DCA) Take-Profit Targets: 0.2821 - 0.2835 - 0.2849 - 0.2891 - 0.2919 - 0.2975 - 0.306 - 0.3228 Stoploss: 0.2639 @MarginScalpsPRO
Showing the 12 most recent of 20 posts we hold for @MarginScalpsPRO. 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.
Named by 2 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Margin Scalps PRO” (@MarginScalpsPRO), 3,719 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/MarginScalpsPRO.
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.