Channel
@snipertradesmanresults
On this record: Growth · Engagement · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001371006787 |
|---|---|
| Type | Channel |
| Username | @snipertradesmanresults |
| Description | Results of the Sniper Tradesman group |
| Created | 26 July 2020 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/snipertradesmanresults |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 17:15 | 3 | no change |
| 6 Aug 2026, 18:07 | 3 | first reading |
4 posts held, back to 26 July 2020 — 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 4 posts for this entry, the most recent from 10 August 2020. An engagement rate over an empty window would be a number about nothing.
Results for the Week: 3 August - 8 August. GbpUsd SL hit (25 pips) 🔻 EurUsd SL hit (20 pips) 🔻 EurAud Breakeven 😒 NzdUsd limit cancelled 🤷🏻♂️ Gold SL hit (20 pips)🔻 Gold TP hit (75 pips) ✅ Gold re-entry Tp hit (47 pips) ✅ Gold TP hit 70 pips ✅ EurUsd limit cancelled 🤷🏻♂️ EurUsd cancelled 🤷🏻♂️ UsdJpy cancelled 🤷🏻♂️ NzdUsd TP hit (40 pips) ✅ EurNzd SL hit (12 pips) 🔻 Gold TP1 hit (60 pips) ✅ Gold TP2 hit (150 pips…
Results for the Week 26 July - 1 August EurUsd SL hit (-16 pips) 🔻 GOLD closed (+120 pips) ✅ UsdCad TP hit (65 pips) ✅ EurUsd TP hit (40 pips) ✅ EurUsd TP2 hit (80 pips) ✅ NzdUsd TP hit (24 pips) ✅ UsdJpy (Limit Missed - Tp hits)🙄 GbpUsd (Limit Missed - Tp hits)🙄 GbpChf SL hit (9 pips) 🔻 GOLD TP hit (420 pips) ✅ GbpUsd TP hit (42 pips) ✅ GbpUsd TP2 hit (122 pips) ✅ EurUsd TP hit (55 pips) ✅ EurUsd TP2 hit (75 pips…
Results for the Week 20 July - 25 July NzdUsd Breakeven 😒 EurUsd Tp hit (50 pips) ✅ UsdCad (Limit Missed - both Tp hits) 🙄 GbpUsd Tp1 hit (50 pips) ✅ GbpUsd Tp2 hit (130 pips) ✅ GbpUsd SL hit (30 pips).🔻 EurCad SL hit (25 pips) 🔻 GbpChf Breakeven (25+ pips) 😒 EurChf Tp hit (25 pips) ✅ GbpUsd Tp missed (+35 pips) ✅ EurUsd Tp hit (40 pips) ✅ EurUsd (Limit Missed - both Tp hits) 🙄 EurAud (Limit Missed - both Tp hits)…
Channel created
Showing the 4 most recent of 4 posts we hold for @snipertradesmanresults. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Sniper Tradesman FX Results” (@snipertradesmanresults), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/snipertradesmanresults.
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.