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

Channel

Crypto Diagonal

@CryptoDiagonal

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

29,373subscribers

-1,945 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002158730648
TypeChannel
Username@CryptoDiagonal
Description🏆 Focused on Developing Strong-Stage Projects ✅ 🔹 We Promote Verified Projects 🔹 #Channnel_Promotions | #Trader | #Investor | #Shills 📶 DM for Marketing/Collab/Business Proposals 👨‍💻 Contact:- @Helpdesk_suppbot
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 October 2026
Measurements held35
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/CryptoDiagonal

Topic

Giveaways & airdrops — 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 9 September 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

29,37331,31830,345.57 August 2026 — 31,318 subscribers8 August 2026 — 31,303 subscribers9 August 2026 — 31,273 subscribers10 August 2026 — 31,239 subscribers11 August 2026 — 31,214 subscribers12 August 2026 — 31,176 subscribers13 August 2026 — 31,155 subscribers15 August 2026 — 31,110 subscribers16 August 2026 — 31,071 subscribers17 August 2026 — 31,044 subscribers18 August 2026 — 31,014 subscribers19 August 2026 — 30,984 subscribers20 August 2026 — 30,952 subscribers21 August 2026 — 30,917 subscribers23 August 2026 — 30,898 subscribers24 August 2026 — 30,857 subscribers25 August 2026 — 30,333 subscribers27 August 2026 — 30,297 subscribers28 August 2026 — 30,274 subscribers28 August 2026 — 30,258 subscribers29 August 2026 — 30,231 subscribers30 August 2026 — 30,205 subscribers1 September 2026 — 30,173 subscribers2 September 2026 — 30,124 subscribers3 September 2026 — 30,078 subscribers5 September 2026 — 30,044 subscribers8 September 2026 — 29,998 subscribers11 September 2026 — 29,984 subscribers13 September 2026 — 29,955 subscribers14 September 2026 — 29,946 subscribers16 September 2026 — 29,926 subscribers18 September 2026 — 29,868 subscribers24 September 2026 — 29,762 subscribers3 October 2026 — 29,490 subscribers8 October 2026 — 29,373 subscribers7 August 20268 October 2026
35 measurements spanning 61 days, net -1,945. 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 29,081–31,610 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
8 Oct 2026, 04:1829,373-117
3 Oct 2026, 16:4129,490-272
24 Sept 2026, 21:5829,762-106
18 Sept 2026, 14:1929,868-58
16 Sept 2026, 05:3929,926-20
14 Sept 2026, 14:2229,946-9
13 Sept 2026, 01:3629,955-29
11 Sept 2026, 04:3829,984-14
8 Sept 2026, 10:1729,998-46
5 Sept 2026, 08:1930,044-34
3 Sept 2026, 08:5230,078-46
2 Sept 2026, 03:2330,124-49
1 Sept 2026, 03:1330,173-32
30 Aug 2026, 23:2930,205-26
29 Aug 2026, 21:5430,231-27
28 Aug 2026, 22:5330,258-16
28 Aug 2026, 02:1530,274-23
27 Aug 2026, 01:2830,297-36
25 Aug 2026, 23:1830,333-524
24 Aug 2026, 22:4630,857first reading

Engagement

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

ERR · 30 days
0.688%
avg views ÷ 29,373 subscribers
Avg views / post
202
127 posts measured
Reaction rate
65.6%
reactions ÷ views · ER floor
Posts in window
127
of 456 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 6 of 127 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 8 October 2026
Posts held456 (13 June 2026 – 8 October 2026)
Views total25,664
Reactions total4,201
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Oct 2026, 23:18 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
232
Videos
2
Links
213

Lifetime counters from Telegram’s own channel header, read 8 October 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
1m 29s
Average length
45s

Measured directly from 2 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

55,495 reactions across 44 posts, in 6 distinct kinds. The most used accounts for 16.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9,39016.9%
🥰9,36616.9%
🔥9,24516.7%
🎉9,23616.6%
❤9,13116.5%
🤩9,12716.4%

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 45 of the 456 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 55,495 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 456 most recent posts we hold, published 13 June 2026 to 8 October 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

4 Oct 2026, 14:30 UTC218 views196 reactionsread 5 October 2026

Posted without readable text

🥰38❤36🔥32🤩31👍30🎉29

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

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

“Crypto Diagonal” (@CryptoDiagonal), 29,373 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/CryptoDiagonal.

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.