Telegram RegisterThe public register of Telegram

Channel

Crypto Tweets

@Crypto_Tweets

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

9,152subscribers

-19 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001204573741
TypeChannel
Username@Crypto_Tweets
Created7 April 2019measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Crypto_Tweets

Growth

9,1529,1729,1626 August 2026 — 9,171 subscribers6 August 2026 — 9,172 subscribers10 August 2026 — 9,164 subscribers12 August 2026 — 9,152 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -19. 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 9,149–9,175 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:589,152-12
10 Aug 2026, 02:119,164-8
6 Aug 2026, 15:259,172+1
6 Aug 2026, 05:359,171first reading

Engagement

20 posts held, back to 17 May 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof 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 17 May 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

16 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16100.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 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 16reactions 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 17 May 2023 to 17 May 2023, 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

17 May 2023, 10:21 UTC≈9,740 views9 reactionsread 12 August 2026

https://twitter.com/aaveaave/status/1658779663668494336 by @Crypto_Tweets

9

17 May 2023, 10:17 UTC≈9,610 views6 reactionsread 12 August 2026

https://twitter.com/axieinfinity/status/1658778828515446784 by @Crypto_Tweets

6

17 May 2023, 10:12 UTC≈9,420 viewsread 12 August 2026

https://twitter.com/axieinfinity/status/1658777431476432896 by @Crypto_Tweets

17 May 2023, 10:11 UTC≈8,700 viewsread 12 August 2026

https://twitter.com/axieinfinity/status/1658777340510367744 by @Crypto_Tweets

17 May 2023, 10:05 UTC≈7,090 viewsread 12 August 2026

https://twitter.com/axieinfinity/status/1658775779092643841 by @Crypto_Tweets

17 May 2023, 10:00 UTC≈5,610 views0 reactionsread 12 August 2026

https://twitter.com/binance/status/1658774361107464193 by @Crypto_Tweets

17 May 2023, 09:52 UTC≈4,600 views1 reactionsread 12 August 2026

https://twitter.com/umaprotocol/status/1658772324609318916 by @Crypto_Tweets

1

17 May 2023, 09:51 UTC≈3,590 viewsread 12 August 2026

https://twitter.com/umaprotocol/status/1658772159110496256 by @Crypto_Tweets

17 May 2023, 09:46 UTC≈3,200 viewsread 12 August 2026

https://twitter.com/iEx_ec/status/1658770864400130048 by @Crypto_Tweets

17 May 2023, 09:36 UTC≈2,640 viewsread 12 August 2026

https://twitter.com/GXChainGlobal/status/1658768320898961409 by @Crypto_Tweets

17 May 2023, 09:34 UTC≈2,160 viewsread 12 August 2026

https://twitter.com/GXChainGlobal/status/1658767961052839937 by @Crypto_Tweets

17 May 2023, 09:20 UTC≈2,010 viewsread 12 August 2026

https://twitter.com/fraxfinance/status/1658764340454129666 by @Crypto_Tweets

Showing the 12 most recent of 20 posts we hold for @Crypto_Tweets. 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 — 233,072 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 5 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Crypto Tweets” (@Crypto_Tweets), 9,152 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Crypto_Tweets.

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.