Channel
FXPIPSKILLER
@FXPIPSKILLER
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,703subscribers
-217 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 | -1001468626745 |
|---|---|
| Type | Channel |
| Username | @FXPIPSKILLER |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/FXPIPSKILLER |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 |
|---|---|---|
| 24 Oct 2026, 23:06 | 3,703 | -9 |
| 21 Oct 2026, 17:29 | 3,712 | -12 |
| 18 Oct 2026, 05:06 | 3,724 | -5 |
| 15 Oct 2026, 11:05 | 3,729 | -9 |
| 12 Oct 2026, 04:36 | 3,738 | -18 |
| 5 Oct 2026, 07:00 | 3,756 | -17 |
| 26 Sept 2026, 18:36 | 3,773 | -25 |
| 17 Sept 2026, 10:20 | 3,798 | -11 |
| 13 Sept 2026, 05:59 | 3,809 | -6 |
| 9 Sept 2026, 14:21 | 3,815 | -15 |
| 6 Sept 2026, 13:28 | 3,830 | no change |
| 4 Sept 2026, 00:00 | 3,830 | -16 |
| 1 Sept 2026, 01:05 | 3,846 | -11 |
| 29 Aug 2026, 04:36 | 3,857 | -6 |
| 26 Aug 2026, 00:27 | 3,863 | -11 |
| 22 Aug 2026, 17:25 | 3,874 | -9 |
| 19 Aug 2026, 15:33 | 3,883 | -12 |
| 16 Aug 2026, 14:06 | 3,895 | -9 |
| 12 Aug 2026, 23:49 | 3,904 | -7 |
| 10 Aug 2026, 09:01 | 3,911 | 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.
@stunnnerv75freetelegram · 40,289
Telegram ranks this channel #19 of 73 here — alongside 72 others — read 30 August 2026
@tonysnip3rcommunity · 58,306
Telegram ranks this channel #41 of 89 here — alongside 88 others — read 24 August 2026
@kiraforexsynth · 28,565
Telegram ranks this channel #42 of 82 here — alongside 81 others — read 9 September 2026
@FXGOAT0 · 111,332
Telegram ranks this channel #62 of 81 here — alongside 80 others — read 16 August 2026
@FXGOAT1 · 120,445
Telegram ranks this channel #77 of 84 here — alongside 83 others — read 14 August 2026
This channel appears in 5 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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“FXPIPSKILLER” (@FXPIPSKILLER), 3,703 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/FXPIPSKILLER.
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.