22 Jan 2026, 09:18 UTC168 viewsread 8 August 2026
#BTCUSD_BUY TP1 HIT 30 PIPS Super Duper
Signed TRADE WITH JAWED
Channel
TRADE WITH EXPERT
@TradeWithexperts16
On this record: Growth · Engagement · Posts · Cite this entry
376subscribers
-7 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 | -1001385942606 |
|---|---|
| Type | Channel |
| Username | @TradeWithexperts16 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/TradeWithexperts16 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 16:29 | 376 | -5 |
| 15 Aug 2026, 09:24 | 381 | -2 |
| 8 Aug 2026, 06:05 | 383 | no change |
| 7 Aug 2026, 16:41 | 383 | first reading |
Engagement
20 posts held, back to 16 January 2026 — 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 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 20 posts for this entry, the most recent from 22 January 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
22 Jan 2026, 09:17 UTC166 viewsread 8 August 2026
#XAUUSD_SELL TP1 HIT 40 PIPS Super Duper
Signed TRADE WITH JAWED
22 Jan 2026, 03:52 UTC171 viewsread 8 August 2026
BTCUSD BUY 89700 TP¹ 89000 TP² 90300 TP³ 90600 TP⁴ 90900 SL 88800
Signed TRADE WITH JAWED
22 Jan 2026, 03:51 UTC170 viewsread 8 August 2026
XAUUSD SELL 4789 TP¹ 4785 TP² 4781 TP³ 4777 TP⁴ 4773 SL 4800
Signed TRADE WITH JAWED
21 Jan 2026, 08:16 UTC153 viewsread 8 August 2026
If you are loosing money in forex contact with me now Let me manage your account @JawedAli1
Signed TRADE WITH JAWED
21 Jan 2026, 08:15 UTC115 viewsread 8 August 2026
#BTCUSD_BUY TP2 HIT 60 PIPS Super Duper
Signed TRADE WITH JAWED
21 Jan 2026, 08:15 UTC106 viewsread 8 August 2026
#BTCUSD_BUY TP1 HIT 30 PIPS Super Duper
Signed TRADE WITH JAWED
21 Jan 2026, 04:25 UTC102 viewsread 8 August 2026
#XAUUSD_SELL TP3 HIT 120 PIPS Super Duper
Signed TRADE WITH JAWED
21 Jan 2026, 04:24 UTC99 viewsread 8 August 2026
#XAUUSD_SELL TP2 HIT 80 PIPS Super Duper
Signed TRADE WITH JAWED
21 Jan 2026, 04:24 UTC94 viewsread 8 August 2026
#XAUUSD_SELL TP1 HIT 40 PIPS Super Duper
Signed TRADE WITH JAWED
21 Jan 2026, 04:18 UTC92 viewsread 8 August 2026
BTCUSD BUY 89300 TP¹ 89600 TP² 89900 TP³ 90200 TP⁴ 90500 SL 88400
Signed TRADE WITH JAWED
21 Jan 2026, 04:14 UTC86 viewsread 8 August 2026
XAUUSD SELL 4850 TP¹ 4846 TP² 4842 TP³ 4838 TP⁴ 4834 SL 4862
Signed TRADE WITH JAWED
Showing the 12 most recent of 20 posts we hold for @TradeWithexperts16. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“TRADE WITH EXPERT” (@TradeWithexperts16), 376 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/TradeWithexperts16.
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.