Telegram RegisterThe public register of Telegram
Telegram profile photo for Cryptocurrencies Channel

Channel

Cryptocurrencies Channel

@cryptocurrency

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

5,010subscribers

-235 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001003016265
TypeChannel
Username@cryptocurrency
Created22 September 2015 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/cryptocurrency

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 14 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@CryptoNewsScooper/625466 Aug 2026, 23:56 UTC@cryptocurrency/112835 · this entry7 Aug 2026, 03:44 UTC1.003.8 hours
@CryptoNewsScooper/625477 Aug 2026, 02:20 UTC@cryptocurrency/112836 · this entry7 Aug 2026, 03:45 UTC1.0085 minutes
@CryptoNewsScooper/625577 Aug 2026, 06:51 UTC@cryptocurrency/112841 · this entry7 Aug 2026, 07:04 UTC1.0012 minutes
@CryptoNewsScooper/625607 Aug 2026, 09:50 UTC@cryptocurrency/112844 · this entry7 Aug 2026, 16:28 UTC1.006.6 hours
@cryptocurrency/112850 · this entry7 Aug 2026, 21:34 UTC@CryptoNewsScooper/625757 Aug 2026, 22:42 UTC1.0068 minutes
@CryptoNewsScooper/625838 Aug 2026, 08:55 UTC@cryptocurrency/112854 · this entry8 Aug 2026, 13:25 UTC1.004.5 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@CryptoNewsScooper33 (8/8 hand-verifiable sample passed)1.0054 minutes@CryptoNewsScooper (24–9)
@thedenofcryptonews6 (6/6 hand-verifiable sample passed)1.003.4 hoursthis entry (6–0)
@CryptoGlobalNetwork5 (5/5 hand-verifiable sample passed)1.0011 minutes@CryptoGlobalNetwork (3–2)
@biergodnews5 (5/5 hand-verifiable sample passed)1.0058 minutes@biergodnews (4–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 31 of the 31 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 76 comparable posts for this entry, running 4 August 2026 to 12 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 14 channels, the one whose matching posts we hold earliest is @bitcoinchannel. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 14 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5,0105,2465,1285 August 2026 — 5,245 subscribers6 August 2026 — 5,246 subscribers6 August 2026 — 5,246 subscribers9 August 2026 — 5,244 subscribers12 August 2026 — 5,241 subscribers15 August 2026 — 5,226 subscribers18 August 2026 — 5,213 subscribers21 August 2026 — 5,209 subscribers24 August 2026 — 5,198 subscribers27 August 2026 — 5,192 subscribers31 August 2026 — 5,184 subscribers2 September 2026 — 5,172 subscribers7 September 2026 — 5,168 subscribers11 September 2026 — 5,156 subscribers15 September 2026 — 5,155 subscribers26 September 2026 — 5,136 subscribers5 October 2026 — 5,104 subscribers12 October 2026 — 5,089 subscribers15 October 2026 — 5,067 subscribers18 October 2026 — 5,061 subscribers21 October 2026 — 5,051 subscribers24 October 2026 — 5,039 subscribers27 October 2026 — 5,037 subscribers30 October 2026 — 5,033 subscribers2 November 2026 — 5,020 subscribers5 November 2026 — 5,019 subscribers8 November 2026 — 5,015 subscribers11 November 2026 — 5,010 subscribers5 August 202611 November 2026
28 measurements spanning 98 days, net -235. 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 4,975–5,281 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
11 Nov 2026, 10:595,010-5
8 Nov 2026, 01:105,015-4
5 Nov 2026, 08:095,019-1
2 Nov 2026, 14:005,020-13
30 Oct 2026, 11:105,033-4
27 Oct 2026, 16:565,037-2
24 Oct 2026, 22:185,039-12
21 Oct 2026, 12:275,051-10
18 Oct 2026, 15:095,061-6
15 Oct 2026, 06:185,067-22
12 Oct 2026, 13:105,089-15
5 Oct 2026, 09:545,104-32
26 Sept 2026, 20:005,136-19
15 Sept 2026, 07:555,155-1
11 Sept 2026, 16:395,156-12
7 Sept 2026, 05:195,168-4
2 Sept 2026, 20:055,172-12
31 Aug 2026, 00:175,184-8
27 Aug 2026, 16:085,192-6
24 Aug 2026, 22:155,198first reading

Engagement

76 posts held, back to 4 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 8 pages 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 76 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

23 reactions across 21 posts, in 7 distinct kinds. The most used accounts for 26.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤626.1%
👏626.1%
👍417.4%
🎉313.0%
💯28.70%
👀14.35%
🙏14.35%

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

Measured over the 76 most recent posts we hold, published 4 August 2026 to 12 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

12 Aug 2026, 01:20 UTC17 viewsread 12 August 2026

Ravencoin hits record low as network exploit puts transactions at risk https://cointelegraph.com/news/ravencoin-rvn-record-low-consensus-exploit?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

12 Aug 2026, 01:19 UTC16 viewsread 12 August 2026

SEC, CFTC sue Goliath Ventures over $400M crypto Ponzi scheme https://cointelegraph.com/news/sec-cftc-sue-goliath-ventures-400m-crypto-ponzi?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 22:39 UTC22 viewsread 12 August 2026

SEC to address crypto regulations in absence of CLARITY passage https://cointelegraph.com/news/sec-crypto-regulations-absence-clarity-act?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 22:38 UTC22 viewsread 12 August 2026

Itaú joins Brazil tokenization pilot with OpenAssets https://cointelegraph.com/news/ita-joins-brazil-tokenization-pilot-with-openassets-brief?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 21:02 UTC22 viewsread 12 August 2026

MoneyGram expands crypto cash ramps to Solana https://cointelegraph.com/news/moneygram-expands-crypto-cash-ramps-to-solana?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 21:01 UTC20 viewsread 12 August 2026

Following Senate delay, crypto bill has a narrow window to become law https://cointelegraph.com/news/clarity-act-senate-delay-window-become-law-midterm-elections?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 21:00 UTC17 viewsread 12 August 2026

Strategy CEO says company will resume Bitcoin accumulation this year https://cointelegraph.com/news/strategy-ceo-resume-bitcoin-accumulation-this-year?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 20:59 UTC15 viewsread 12 August 2026

ARP Digital secures Dubai VARA broker-dealer license https://cointelegraph.com/news/arp-digital-secures-dubai-vara-broker-dealer-license?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 17:46 UTC27 viewsread 12 August 2026

FlightAware sues Kalshi over flight cancellation data https://cointelegraph.com/news/flightaware-lawsuit-kalshi-flight-cancellations?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 17:45 UTC23 viewsread 12 August 2026

Coinbase-backed Flowdesk secures full broker-dealer license in Dubai https://cointelegraph.com/news/flowdesk-dubai-vara-broker-dealer-license?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 17:44 UTC22 viewsread 12 August 2026

Nasdaq to acquire LeveL Markets in push toward ‘always-on’ markets https://cointelegraph.com/news/nasdaq-to-acquire-level-markets-in-push-toward-always-on-markets?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

11 Aug 2026, 17:43 UTC21 viewsread 12 August 2026

Bitcoin drops to one-week low as retail buys gold at highest prices since June https://cointelegraph.com/markets/bitcoin-drops-to-one-week-low-as-retail-buys-gold-at-highest-prices-since-june?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound

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

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.

MRCP ROAD - PART TWO
@DrOsamaMrcpPart2 · 18,728
Telegram ranks this channel #38 of 71 here — alongside 70 others — read 5 October 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Cryptocurrencies Channel” (@cryptocurrency), 5,010 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/cryptocurrency.

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.