Telegram RegisterThe public register of Telegram

Channel

Crypto Crown ™

@CryptoCrownTM

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

36,699subscribers

-80 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001215365882
TypeChannel
Username@CryptoCrownTM
DescriptionEducational coverage of blockchain ecosystems, digital assets, and web3 trends since 2021. Focus on technological research, industry insights, and foundational mechanics.
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/CryptoCrownTM

Growth

36,69936,77936,7397 August 2026 — 36,779 subscribers7 August 2026 — 36,779 subscribers8 August 2026 — 36,762 subscribers9 August 2026 — 36,758 subscribers10 August 2026 — 36,730 subscribers11 August 2026 — 36,721 subscribers12 August 2026 — 36,705 subscribers13 August 2026 — 36,699 subscribers7 August 202613 August 2026
8 measurements spanning 6 days, net -80. 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 36,687–36,791 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:4436,699-6
12 Aug 2026, 03:3436,705-16
11 Aug 2026, 04:4436,721-9
10 Aug 2026, 04:2336,730-28
9 Aug 2026, 05:0236,758-4
8 Aug 2026, 04:1536,762-17
7 Aug 2026, 02:5736,779no change
7 Aug 2026, 00:3236,779first reading

Engagement

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

ERR · 30 days
3.46%
avg views ÷ 36,699 subscribers
Avg views / post
1,270
58 posts measured
Reaction rate
2.12%
reactions ÷ views · ER floor
Posts in window
59
of 59 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held59 (3 August 202613 August 2026)
Views total73,660
Reactions total1,559
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 09:23 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
2,980
Videos
8
Links
911

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

1,559 reactions across 58 posts, in 8 distinct kinds. The most used accounts for 57.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍88857.0%
30619.6%
🔥1419.04%
🐳966.16%
💯634.04%
🤝392.50%
🤯201.28%
60.385%

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 58 of the 59 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 1,559reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 59 most recent posts we hold, published 3 August 2026 to 13 August 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

13 Aug 2026, 05:57 UTC382 views19 reactionsread 13 August 2026
Photo

#1MBABYDOGE — the market structure looks like it’s shifting lower. 👨‍💻 I’ll be watching the highlighted area closely if price returns there!🫰

👍115🔥3

12 Aug 2026, 16:07 UTC899 views30 reactionsread 13 August 2026
Photo

#BTC — momentum doesn’t look strong enough to clear the highs, and price seems more drawn toward the sell-side liquidity. 😕 If 61K gets reached, I’ll update the view based on the reaction there.🥇

👍20🐳4🔥32💯1

12 Aug 2026, 16:02 UTC879 views19 reactionsread 13 August 2026

I was a bit unsure about updating you since price didn’t reach the zone I had in mind, but I’ll share what I’m seeing.😈

👍19

12 Aug 2026, 12:30 UTC≈1,030 views23 reactionsread 13 August 2026

🚨 BREAKING: 🇺🇸 US inflation falls to 3.4%.

👍202💯1

12 Aug 2026, 09:57 UTC≈1,130 views25 reactionsread 13 August 2026
Photo

#ETH — price is still ranging between these two levels, with buyers showing more strength. 🕔 If you missed the lower level, it’s better to wait for price to reach one of these areas again.✅

👍16🔥4💯32

12 Aug 2026, 06:01 UTC≈1,180 views26 reactionsread 13 August 2026
Photo

#NEAR — keep an eye on this guy. 😈 The demand area reacted nicely, and getting back above the range would be an interesting sign for further upside.✍️.

👍20🐳32🔥1

11 Aug 2026, 19:53 UTC≈1,240 views19 reactionsread 13 August 2026

🚨JUST IN: 🇺🇸 SEC to unveil major crypto plans, Bloomberg reports.

👍153🔥1

11 Aug 2026, 14:11 UTC≈1,320 views24 reactionsread 13 August 2026
Photo

#RUNE — this guy gave a nice reaction from the entry area! 😕 Hopefully, it keeps moving as planned. 🤝

👍172🔥2🤝2🤯1

11 Aug 2026, 13:37 UTC≈1,260 views32 reactionsread 13 August 2026

About our new system 😈 It’s built around my BTC charting approach, and we’re working on bringing it to you as a simple setup-style system, available for free on two exchanges. We’re still testing and reviewing everything for now. Stay tuned! 🤝

👍255🤝2

11 Aug 2026, 10:03 UTC≈1,290 views24 reactionsread 13 August 2026
Photo

#ZEC — liquidity was taken as planned , guys!😈 My expectation is for price to continue toward the sell-side liquidity.❣️

🐳146👍4

11 Aug 2026, 05:58 UTC≈1,290 views26 reactionsread 13 August 2026
Photo

#GOLD — liquidity above the highs was taken as expected, and we got the initial reaction. 😄 Now let’s see what the next move looks like.✅

👍175💯4

10 Aug 2026, 16:17 UTC≈1,320 views25 reactionsread 13 August 2026
Photo

#ATOM — another clean move played out nicely. 👍 Enjoy, guys! 🤝

👍154🐳3🔥2💯1

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

Citation-graph rank

Citation-graph rank — 179,168 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 6 registered channels — 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.

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.

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

“Crypto Crown ™” (@CryptoCrownTM), 36,699 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/CryptoCrownTM.

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.