Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Desk

Channel

Crypto Desk

@Crypto_Desk_Signals

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Cite this entry

199,811subscribers

-5,137 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1003808387847
TypeChannel
Username@Crypto_Desk_Signals
DescriptionCrypto Desk 📊 Professional trading setups & market analysis BTC • ETH • Altcoins Clear entries • Targets • Risk management Not financial advice. DYOR.
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live24 September 2026
Measurements held21
Confirmed unchanged1 time, most recently 24 September 2026
On Telegramt.me/Crypto_Desk_Signals

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 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 why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far below this size band

19.6 average views per post against 199,811 subscribers — an engagement rate of 0.01%. Across the 1,172 registered channels in the same cohort — 100,014–314,959 subscribers, posting mainly in English — the middle half sit between 0.922% and 8.77%, with a median of 3.44%.

What this was computed from
Window30 days (30 August 2026 – 29 September 2026)
Posts measured258 of 258 published in the window (258 exact, 0 rounded by Telegram)
Views totalled5,064
Mature posts only0.017% over 122 posts read at least 24h after publication
Subscribers199,811 measured 24 September 2026
Cohortb100000:eng · 1,172 channels · p10 0.284% · p25 0.922% · p50 3.44% · p75 8.77% · p90 16.7%
Position in cohort0.769th percentile · 1/333 the cohort median
Uncertainty±0% of the figure, from Telegram’s rounding
Post languageEnglish · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_low, last confirmed 29 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

199,811205,462202,636.57 August 2026 — 204,948 subscribers8 August 2026 — 204,948 subscribers14 August 2026 — 204,949 subscribers15 August 2026 — 204,948 subscribers17 August 2026 — 204,947 subscribers18 August 2026 — 204,935 subscribers19 August 2026 — 204,932 subscribers21 August 2026 — 204,931 subscribers30 August 2026 — 204,930 subscribers31 August 2026 — 204,928 subscribers1 September 2026 — 204,913 subscribers2 September 2026 — 204,902 subscribers3 September 2026 — 201,067 subscribers4 September 2026 — 201,039 subscribers7 September 2026 — 200,947 subscribers11 September 2026 — 205,462 subscribers13 September 2026 — 204,995 subscribers14 September 2026 — 204,729 subscribers16 September 2026 — 204,054 subscribers18 September 2026 — 201,588 subscribers24 September 2026 — 199,811 subscribers7 August 202624 September 2026
21 measurements spanning 48 days, net -5,137. 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 198,963–206,310 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
24 Sept 2026, 21:21199,811-1,777
18 Sept 2026, 15:21201,588-2,466
16 Sept 2026, 07:00204,054-675
14 Sept 2026, 14:01204,729-266
13 Sept 2026, 00:19204,995-467
11 Sept 2026, 00:41205,462+4,515
7 Sept 2026, 23:21200,947-92
4 Sept 2026, 22:41201,039-28
3 Sept 2026, 09:33201,067-3,835
2 Sept 2026, 05:14204,902-11
1 Sept 2026, 05:24204,913-15
31 Aug 2026, 06:54204,928-2
30 Aug 2026, 09:03204,930-1
21 Aug 2026, 01:34204,931-1
19 Aug 2026, 04:55204,932-3
18 Aug 2026, 07:57204,935-12
17 Aug 2026, 09:29204,947-1
15 Aug 2026, 20:17204,948-1
14 Aug 2026, 13:14204,949+1
8 Aug 2026, 02:35204,948first reading

Engagement

576 posts held, back to 7 August 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 111 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.009%
avg views ÷ 199,811 subscribers
Avg views / post
18.7
271 posts measured
Reaction rate
50.0%
reactions ÷ views · ER floor
Posts in window
271
of 576 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 271 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 September 2026
Posts held576 (7 August 2026 – 29 September 2026)
Views total5,070
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 20:36 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
540
Videos
25
Links
34

Lifetime counters from Telegram’s own channel header, read 29 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
8m 54s
Average length
25s

Measured directly from 21 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3100.0%

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 4 of the 576 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 576 most recent posts we hold, published 7 August 2026 to 29 September 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

29 Sept 2026, 20:06 UTC1 viewsread 29 September 2026

Invested? $2.1K Made? $34K.. But why does it show +7,014? That’s cuz it’s a bundle. I sold from different wallets.

29 Sept 2026, 20:06 UTC1 viewsread 29 September 2026

Invested? $1.2K Made? $60K.. But why does it show +10,887? That’s cuz it’s a bundle. I sold from different wallets.

29 Sept 2026, 19:30 UTC2 viewsread 29 September 2026

Invested? $2.1K Made? $34K.. But why does it show +7,014? That’s cuz it’s a bundle. I sold from different wallets.

Showing the 12 most recent of 576 posts we hold for @Crypto_Desk_Signals. 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.

Posts edited after publishing

@Crypto_Desk_Signals edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
20 August 2026
Most recent edit
20 August 2026

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 September 2026 — this entry's latest reading, not the date you are reading this.

“Crypto Desk” (@Crypto_Desk_Signals), 199,811 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/Crypto_Desk_Signals.

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.