Channel
GOLD US30 KILLER
@Joan_FX_KING_77
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,047subscribers
+185 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001687301463 |
|---|---|
| Type | Channel |
| Username | @Joan_FX_KING_77 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/Joan_FX_KING_77 |
Topic
Other / unclassifiable — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 08:59 | 4,047 | -4 |
| 4 Nov 2026, 04:17 | 4,051 | -2 |
| 1 Nov 2026, 12:45 | 4,053 | +2 |
| 29 Oct 2026, 19:39 | 4,051 | +32 |
| 26 Oct 2026, 10:46 | 4,019 | +10 |
| 23 Oct 2026, 12:45 | 4,009 | +32 |
| 20 Oct 2026, 05:00 | 3,977 | +4 |
| 17 Oct 2026, 06:28 | 3,973 | +3 |
| 13 Oct 2026, 20:58 | 3,970 | +6 |
| 8 Oct 2026, 11:41 | 3,964 | +7 |
| 1 Oct 2026, 19:16 | 3,957 | +52 |
| 16 Sept 2026, 17:39 | 3,905 | -9 |
| 12 Sept 2026, 17:55 | 3,914 | -4 |
| 8 Sept 2026, 14:40 | 3,918 | +45 |
| 6 Sept 2026, 00:14 | 3,873 | no change |
| 3 Sept 2026, 00:25 | 3,873 | +11 |
| 30 Aug 2026, 15:15 | 3,862 | 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.
@vipgoldsignals_1778 · 28,477
Telegram ranks this channel #20 of 50 here — alongside 49 others — read 10 September 2026
@goldplatinum_trader · 39,164
Telegram ranks this channel #37 of 50 here — alongside 49 others — read 2 September 2026
@tradewithzafrre · 22,951
Telegram ranks this channel #46 of 54 here — alongside 53 others — read 17 September 2026
@eti_algos · 1,979
Telegram ranks this channel #57 of 59 here — alongside 58 others — read 30 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“GOLD US30 KILLER” (@Joan_FX_KING_77), 4,047 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/Joan_FX_KING_77.
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.