Channel
XTrading Señales
@xtradingsignalss
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,630subscribers
-18 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001839629637 |
|---|---|
| Type | Channel |
| Username | @xtradingsignalss |
| Description | CANAL DEDICADO A ÍNDICES SINTÉTICOS BOOM Y CRASH ✅SOLO SEÑALES ESCRITAS ✅ANÁLISIS TÉCNICO ✅ENTRADAS DE ROMPIMIENTO ❌NO OPERAMOS VELAS TREND 100% GRATIS VIP @AlexanderPcc |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 13 |
| On Telegram | t.me/xtradingsignalss |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 25 Sept 2026, 23:50 | 1,630 | no change |
| 19 Sept 2026, 13:21 | 1,630 | -3 |
| 15 Sept 2026, 02:16 | 1,633 | -4 |
| 11 Sept 2026, 13:58 | 1,637 | +3 |
| 7 Sept 2026, 01:38 | 1,634 | -6 |
| 2 Sept 2026, 14:18 | 1,640 | -7 |
| 30 Aug 2026, 20:07 | 1,647 | -2 |
| 27 Aug 2026, 20:35 | 1,649 | +5 |
| 24 Aug 2026, 17:59 | 1,644 | -3 |
| 20 Aug 2026, 15:51 | 1,647 | -2 |
| 17 Aug 2026, 15:58 | 1,649 | +3 |
| 11 Aug 2026, 05:41 | 1,646 | -2 |
| 7 Aug 2026, 17:31 | 1,648 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
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.
@Deriv_Volatility_Signals · 26,496
Telegram ranks this channel #12 of 37 here — alongside 36 others — read 12 September 2026
@zertrade · 191,401
Telegram ranks this channel #18 of 50 here — alongside 49 others — read 11 August 2026
@speechless_secret · 240,251
Telegram ranks this channel #26 of 58 here — alongside 57 others — read 30 August 2026
@trader_trading_senales_forex · 64,377
Telegram ranks this channel #27 of 62 here — alongside 61 others — read 27 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“XTrading Señales” (@xtradingsignalss), 1,630 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/xtradingsignalss.
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.