Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Signals Premium

Channel

Crypto Signals Premium

@cryptosignalsdiscord

Not marked by Telegram, checked 29 September 2026

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

692subscribers

-46 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002244040719
TypeChannel
Username@cryptosignalsdiscord
CreatedBetween 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/cryptosignalsdiscord

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

6927387157 August 2026 — 738 subscribers8 August 2026 — 738 subscribers14 August 2026 — 735 subscribers26 August 2026 — 732 subscribers3 September 2026 — 730 subscribers12 September 2026 — 727 subscribers25 September 2026 — 719 subscribers6 October 2026 — 705 subscribers14 October 2026 — 702 subscribers21 October 2026 — 700 subscribers27 October 2026 — 698 subscribers2 November 2026 — 695 subscribers10 November 2026 — 692 subscribers7 August 202610 November 2026
13 measurements spanning 95 days, net -46. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 685–745 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 23:17692-3
2 Nov 2026, 21:46695-3
27 Oct 2026, 18:20698-2
21 Oct 2026, 14:12700-2
14 Oct 2026, 09:37702-3
6 Oct 2026, 10:37705-14
25 Sept 2026, 03:22719-8
12 Sept 2026, 03:39727-3
3 Sept 2026, 19:20730-2
26 Aug 2026, 15:18732-3
14 Aug 2026, 08:37735-3
8 Aug 2026, 02:03738no change
7 Aug 2026, 13:02738first reading

Engagement

20 posts held, back to 1 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

7 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥457.1%
🏆228.6%
⚡114.3%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 5 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 1 June 2026 to 10 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

10 Jul 2026, 11:15 UTC185 views2 reactionsread 8 August 2026
Photo

ONLY IF, OPUSDT Update: 4h Only if we manage to break from above of the dashed trend, we will see a very strong bullish move, and reversal in trend to the upside.

🏆2

10 Jul 2026, 11:15 UTC138 viewsread 8 August 2026
Photo

$APTUSDT Update: Consolidating below of the resistance, if we manage to break from above we will see a strong move to the upside until the price of $0.7

10 Jul 2026, 11:15 UTC161 viewsread 8 August 2026
Photo

$ETHUSDT Update: Currently retesting a HIDDEN dashed trend as you can see. We are consolidating, if we manage to BREAK and HOLD above in the 4 hours timeframe, we'd be expecting to see a strong move to the upside. 💹

10 Jul 2026, 11:15 UTC185 viewsread 8 August 2026
Photo

$BCHUSDT Update: 4h Currently forming a rounding bottom bullish pattern, and broken from above of a hidden downtrend, if we manage to break the $250 resistance, we could be expecting a strong move to the upside atleast until the price of $300

10 Jul 2026, 11:15 UTC127 viewsread 8 August 2026
Photo

$SUIUSDT Update: Currently consolidating a little bit above of the two strong resistances we have, the horizontal, and the trendline. Expecting to see a strong move to the upside real soon if we hold here. 💹

18 Jun 2026, 15:58 UTC227 viewsread 8 August 2026
Photo

$BTCUSDT Update: 1h Lost the trendline, expecting it to sink lower from here. 📉

18 Jun 2026, 15:58 UTC193 viewsread 8 August 2026

so the second scenario is on, which is a new bearish trendline.

18 Jun 2026, 15:58 UTC194 viewsread 8 August 2026

retest prediction went corrrect but unfortunately we could hold

18 Jun 2026, 15:39 UTC191 viewsread 8 August 2026
Photo

$BTCUSDT Update: 1h Lost the trendline, expecting it to sink lower from here. 📉

17 Jun 2026, 12:10 UTC187 viewsread 8 August 2026
Photo

$ETHUSDT Update: 2h Currently heading to the dashed trendline, expecting for Ethereum to retest around the price of $1,720

17 Jun 2026, 12:08 UTC168 viewsread 8 August 2026
Photo

Bitcoin almost followed our first prediction, but now we havea new point of vision, we will retest the rectangle uptrend support.

12 Jun 2026, 12:30 UTC236 views1 reactionsread 8 August 2026
Photo

$BTCUSDT Update: 1h I don't see anything special yet in Bitcoin's chart, if you have shorted the big move with us, just stay safe and scalp a little bit only, keep your profits secure by not entering risky positions for no reason and wanting to make profits real quick. Now it's not the time, just small points.

🔥1

Showing the 12 most recent of 20 posts we hold for @cryptosignalsdiscord. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

CryptoNinjas Trading 🥷🏿
@cryptoninjas_trading_ann · 20,295
Telegram ranks this channel #10 of 76 here — alongside 75 others — read 28 September 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Crypto Signals Premium” (@cryptosignalsdiscord), 692 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/cryptosignalsdiscord.

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.