Channel
CryptoSignals.Org
@Cryptosignals_Org01
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,613subscribers
-188 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001577597706 |
|---|---|
| Type | Channel |
| Username | @Cryptosignals_Org01 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/Cryptosignals_Org01 |
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 91% 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 |
|---|---|---|
| 3 Nov 2026, 16:24 | 3,613 | -6 |
| 1 Nov 2026, 00:19 | 3,619 | -6 |
| 28 Oct 2026, 21:32 | 3,625 | -12 |
| 25 Oct 2026, 21:56 | 3,637 | -6 |
| 23 Oct 2026, 03:47 | 3,643 | -6 |
| 20 Oct 2026, 13:17 | 3,649 | -12 |
| 17 Oct 2026, 16:28 | 3,661 | -7 |
| 14 Oct 2026, 09:51 | 3,668 | -5 |
| 11 Oct 2026, 04:16 | 3,673 | -9 |
| 4 Oct 2026, 20:15 | 3,682 | -28 |
| 25 Sept 2026, 01:19 | 3,710 | -12 |
| 16 Sept 2026, 12:18 | 3,722 | -10 |
| 12 Sept 2026, 08:37 | 3,732 | -12 |
| 8 Sept 2026, 01:58 | 3,744 | -11 |
| 6 Sept 2026, 22:47 | 3,755 | no change |
| 2 Sept 2026, 16:59 | 3,755 | -10 |
| 30 Aug 2026, 18:07 | 3,765 | -5 |
| 27 Aug 2026, 12:25 | 3,770 | -3 |
| 24 Aug 2026, 07:52 | 3,773 | -1 |
| 20 Aug 2026, 17:42 | 3,774 | 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.
@wolfxsignals_freee · 36,292
Telegram ranks this channel #1 of 46 here — alongside 45 others — read 1 September 2026
@Cryptobantergroup0 · 74,672
Telegram ranks this channel #1 of 67 here — alongside 66 others — read 23 August 2026
@LadyofcryptoCommunity · 101,065
Telegram ranks this channel #11 of 50 here — alongside 49 others — read 15 August 2026
@cryptotipstrick · 18,090
Telegram ranks this channel #16 of 75 here — alongside 74 others — read 27 September 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“CryptoSignals.Org” (@Cryptosignals_Org01), 3,613 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Cryptosignals_Org01.
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.