Channel
Top Signal Leak by @tslforexshop
@topsignalleak
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,358subscribers
+73 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 | -1001745111368 |
|---|---|
| Type | Channel |
| Username | @topsignalleak |
| Description | No1 Top Signal Leak Admin: @fxtoolsnetCS Signal List: https://topsignalleaks.netlify.app Feedback: https://t.me/tslforexshop/497 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 15 |
| On Telegram | t.me/topsignalleak |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 1 Oct 2026, 00:50 | 1,358 | no change |
| 27 Sept 2026, 04:40 | 1,358 | +19 |
| 17 Sept 2026, 18:00 | 1,339 | +5 |
| 13 Sept 2026, 14:00 | 1,334 | +3 |
| 9 Sept 2026, 15:18 | 1,331 | -2 |
| 4 Sept 2026, 12:17 | 1,333 | +6 |
| 1 Sept 2026, 01:07 | 1,327 | +8 |
| 29 Aug 2026, 02:15 | 1,319 | +5 |
| 26 Aug 2026, 06:22 | 1,314 | +3 |
| 23 Aug 2026, 10:23 | 1,311 | +7 |
| 17 Aug 2026, 12:54 | 1,304 | +6 |
| 14 Aug 2026, 04:08 | 1,298 | +8 |
| 10 Aug 2026, 19:28 | 1,290 | +4 |
| 8 Aug 2026, 05:20 | 1,286 | +1 |
| 7 Aug 2026, 09:58 | 1,285 | 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.
@forexbrokersignal · 31,662
Telegram ranks this channel #15 of 77 here — alongside 76 others — read 5 September 2026
@Ash_TheTrader · 19,796
Telegram ranks this channel #19 of 71 here — alongside 70 others — read 30 September 2026
@RioTraders · 78,021
Telegram ranks this channel #29 of 77 here — alongside 76 others — read 20 August 2026
@Fxx25pipss · 22,819
Telegram ranks this channel #43 of 66 here — alongside 65 others — read 20 September 2026
@smartearnersacademyllc · 24,921
Telegram ranks this channel #54 of 73 here — alongside 72 others — read 6 September 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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Top Signal Leak by @tslforexshop” (@topsignalleak), 1,358 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/topsignalleak.
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.