SELL GBPCAD ENTRY 1.8558 SL 1.8628 TP 1.8538 TP 1.8508 TP 1.8458

Channel
Callisto Fx
@callistofxx01
On this record: Topic · Growth · Engagement · Posts · Cite this entry
164subscribers
-5 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 | -1001730170421 |
|---|---|
| Type | Channel |
| Username | @callistofxx01 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/callistofxx01 |
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 25 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 |
|---|---|---|
| 11 Oct 2026, 01:20 | 164 | -1 |
| 30 Sept 2026, 08:16 | 165 | -2 |
| 8 Sept 2026, 06:59 | 167 | -2 |
| 8 Aug 2026, 15:16 | 169 | no change |
| 7 Aug 2026, 08:54 | 169 | first reading |
Engagement
20 posts held, back to 20 May 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 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 4 June 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
SELL NZDCHF ENTRY 0.4916 SL 0.4986 TP 0.4895 TP 0.4866 TP 0.4816
BUY BTCUSD ENTRY 105360.00 SL 104660.00 TP 105560.00 TP 105860.00 TP 106360.00
BUY BTCUSD ENTRY 104850.00 SL 104150.00 TP 105050.00 TP 105350.00 TP 105850.00
SELL CADJPY ENTRY 104.13 SL 104.83 TP 103.93 TP 103.63 TP 103.13
SELL GBPUSD ENTRY 1.3460 SL 1.3530 TP 1.3440 TP 1.3410 TP 1.3360
SELL EURJPY ENTRY 163.23 SL 163.92 TP 163.03 TP 162.73 TP 162.23
BUY NZDUSD ENTRY 0.5965 SL 0.5895 TP 0.5985 TP 0.6015 TP 0.6065
BUY AUDUSD ENTRY 0.6441 SL 0.6371 TP 0.6461 TP 0.6491 TP 0.6541
BUY BTCUSD ENTRY 107840.00 SL 107140.00 TP 108040.00 TP 108340.00 TP 108840.00
BUY BTCUSD ENTRY 108810.00 SL 108110.00 TP 109010.00 TP 109310.00 TP 109810.00
(28.MAY.2025) Today's Free Signal XAUUSD BUY TP3 HITS 100+ PIPS 🔥🔥🔥🤑🤑 LETS GO❗
Showing the 12 most recent of 20 posts we hold for @callistofxx01. 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Callisto Fx” (@callistofxx01), 164 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/callistofxx01.
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.