Channel
Gold scalper
@Gold_sxalper90
On this record: Topic · Previous handles · Growth · Engagement · Telegram's recommendations · Cite this entry
3,480subscribers
-227 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001322099805 |
|---|---|
| Type | Channel |
| Username | @Gold_sxalper90 |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/Gold_sxalper90 |
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 5 October 2026 and assigned it the closest of 31 fixed categories, at 79% 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 the other topics.
Previous handles
@Gold_sxalper90 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 7 September 2026 – 7 September 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 14:06 | 3,480 | -8 |
| 3 Nov 2026, 15:31 | 3,488 | -5 |
| 31 Oct 2026, 13:21 | 3,493 | -5 |
| 28 Oct 2026, 13:39 | 3,498 | -7 |
| 25 Oct 2026, 20:18 | 3,505 | -7 |
| 23 Oct 2026, 01:31 | 3,512 | -6 |
| 20 Oct 2026, 09:16 | 3,518 | -9 |
| 17 Oct 2026, 00:10 | 3,527 | -8 |
| 13 Oct 2026, 20:44 | 3,535 | -14 |
| 8 Oct 2026, 09:20 | 3,549 | -14 |
| 5 Oct 2026, 00:23 | 3,563 | no change |
| 4 Oct 2026, 20:17 | 3,563 | -81 |
| 7 Sept 2026, 13:15 | 3,644 | no change |
| 6 Sept 2026, 17:40 | 3,644 | -8 |
| 1 Sept 2026, 20:05 | 3,652 | -6 |
| 29 Aug 2026, 12:27 | 3,658 | -4 |
| 26 Aug 2026, 08:46 | 3,662 | -5 |
| 23 Aug 2026, 07:04 | 3,667 | -5 |
| 19 Aug 2026, 13:59 | 3,672 | -6 |
| 16 Aug 2026, 16:14 | 3,678 | 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.
@JessicalyamXauUsdSignals · 19,271
Telegram ranks this channel #47 of 69 here — alongside 68 others — read 4 October 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Gold scalper” (@Gold_sxalper90), 3,480 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/Gold_sxalper90.
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.