#SOL/USDT Take-Profit target 3✅ Profit: 200% 📈 🌟 10x Leverage 💫 Period: ~4DAYS ⏰

Channel
Binance pro trader TA and VIP results
@binance_pro_trader_results
On this record: Topic · Growth · Engagement · Posts · Cite this entry
100subscribers
-1 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 | -1001534296215 |
|---|---|
| Type | Channel |
| Username | @binance_pro_trader_results |
| Created | Between 1 August 2021 and 6 December 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 8 October 2026 |
| On Telegram | t.me/binance_pro_trader_results |
Topic
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 27 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 17:39 | 100 | -1 |
| 9 Aug 2026, 10:16 | 101 | no change |
| 7 Aug 2026, 00:42 | 101 | first reading |
Engagement
20 posts held, back to 6 December 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 25 March 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
#ADA/USDT Take-Profit target 1🎯 ✅ Profit: 10%🔥📈 Period: ~10hours #SPOT🤝
#SRM/USDT Take-Profit target 2🎯 ✅ Profit: 14%🔥📈 Period: ~14hours #SPOT
#NULs/USDT Take-Profit target 1 ✅ Profit: 3.80% 📈 Period: #SPOT
#SOL/USDT Take-Profit target 1 ✅ Profit: 90% 📈 🌟 10x Leverage 💫 Period: ~2 DAYS ⏰
#DOT/USDT Take-Profit target 1 ✅ Profit: 5.0% 📈 Period: 6 Hours
#BTC/USDT Take-Profit target 1 ✅ Profit: 25% 📈 Period: 12 Hours ⏰
#SRM/USDT Take-Profit target 1 ✅ Profit: 7.57% 📈 Period: 4Hours #SPOT
#ETH/USDT Take-Profit target 1 ✅ Profit: 50.0% 📈
#zrx/USDT Take-Profit target 1 ✅ Profit: 6%📈 Period: ~30Minutes ⏰
#GALA/USDT Take-Profit target 1 ✅ Profit: 22%📈 Period: ~22Hours ⏰
19% ⬆️ up 🆙 From our entry ✅🔥🚀🤝
Showing the 12 most recent of 20 posts we hold for @binance_pro_trader_results. 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Binance pro trader TA and VIP results” (@binance_pro_trader_results), 100 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/binance_pro_trader_results.
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.