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

Channel

Crypto Tracker

@TrakerCrypto

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

9,353subscribers

-3,157 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001768110355
TypeChannel
Username@TrakerCrypto
DescriptionSuscríbete sin falta a mi canal. Aquí hablo de mi negocio y de mi filosofía de vida, y comparto datos útiles y material formativo. Solo bitcoin, solo criptomonedas, solo hardcore.
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 November 2026
Measurements held48
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/TrakerCrypto

Topic

Crypto & trading — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@cryptodaily/1123910 Aug 2026, 08:17 UTC@TrakerCrypto/1890 · this entry15 Aug 2026, 20:38 UTC1.006 days
@cryptodaily/1125313 Aug 2026, 08:32 UTC@TrakerCrypto/1893 · this entry19 Aug 2026, 20:38 UTC1.007 days
@cryptodaily/1125212 Aug 2026, 17:02 UTC@TrakerCrypto/1894 · this entry19 Aug 2026, 20:39 UTC1.007 days
@cryptodaily/112389 Aug 2026, 15:02 UTC@TrakerCrypto/1891 · this entry15 Aug 2026, 20:38 UTC0.986 days
@cryptodaily/112368 Aug 2026, 13:17 UTC@TrakerCrypto/1892 · this entry15 Aug 2026, 20:38 UTC0.977 days
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
@cryptodaily5 (5/5 hand-verifiable sample passed)0.997 days@cryptodaily (5–0)

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. 5 of the 5 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 67 comparable posts for this entry, running 17 July 2026 to 10 November 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).

Recorded under the key clone_copy, 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.

Growth

9,35312,51010,931.57 August 2026 — 12,510 subscribers8 August 2026 — 12,510 subscribers8 August 2026 — 12,493 subscribers9 August 2026 — 12,475 subscribers10 August 2026 — 12,396 subscribers11 August 2026 — 12,369 subscribers12 August 2026 — 12,347 subscribers13 August 2026 — 12,233 subscribers14 August 2026 — 12,102 subscribers16 August 2026 — 12,059 subscribers17 August 2026 — 11,995 subscribers18 August 2026 — 11,896 subscribers19 August 2026 — 11,737 subscribers20 August 2026 — 11,721 subscribers21 August 2026 — 11,712 subscribers23 August 2026 — 11,692 subscribers24 August 2026 — 11,646 subscribers25 August 2026 — 11,586 subscribers26 August 2026 — 11,569 subscribers27 August 2026 — 11,564 subscribers28 August 2026 — 11,555 subscribers29 August 2026 — 11,541 subscribers30 August 2026 — 11,531 subscribers31 August 2026 — 11,492 subscribers1 September 2026 — 11,436 subscribers2 September 2026 — 11,406 subscribers4 September 2026 — 11,382 subscribers7 September 2026 — 11,281 subscribers10 September 2026 — 11,200 subscribers12 September 2026 — 11,154 subscribers14 September 2026 — 11,130 subscribers15 September 2026 — 11,125 subscribers17 September 2026 — 11,109 subscribers27 September 2026 — 10,591 subscribers4 October 2026 — 10,214 subscribers9 October 2026 — 10,032 subscribers13 October 2026 — 10,022 subscribers14 October 2026 — 10,015 subscribers15 October 2026 — 10,000 subscribers16 October 2026 — 9,992 subscribers19 October 2026 — 9,984 subscribers23 October 2026 — 9,971 subscribers26 October 2026 — 9,953 subscribers29 October 2026 — 9,899 subscribers1 November 2026 — 9,794 subscribers4 November 2026 — 9,677 subscribers7 November 2026 — 9,520 subscribers11 November 2026 — 9,353 subscribers7 August 202611 November 2026
48 measurements spanning 96 days, net -3,157. 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 8,879–12,984 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
11 Nov 2026, 22:589,353-167
7 Nov 2026, 23:469,520-157
4 Nov 2026, 22:119,677-117
1 Nov 2026, 14:169,794-105
29 Oct 2026, 15:599,899-54
26 Oct 2026, 13:279,953-18
23 Oct 2026, 05:019,971-13
19 Oct 2026, 19:489,984-8
16 Oct 2026, 20:119,992-8
15 Oct 2026, 17:4610,000-15
14 Oct 2026, 19:3810,015-7
13 Oct 2026, 10:4110,022-10
9 Oct 2026, 10:2110,032-182
4 Oct 2026, 22:0110,214-377
27 Sept 2026, 16:0110,591-518
17 Sept 2026, 17:4111,109-16
15 Sept 2026, 18:1711,125-5
14 Sept 2026, 05:1711,130-24
12 Sept 2026, 12:0011,154-46
10 Sept 2026, 08:3611,200first reading

Engagement

70 posts held, back to 17 July 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 60 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
39.5%
avg views ÷ 9,353 subscribers
Avg views / post
3,700
27 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
27
of 70 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 10 November 2026
Posts held70 (17 July 2026 – 10 November 2026)
Views total99,810
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 23:40 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
≈1,170
Videos
≈43
Links
≈888

Lifetime counters from Telegram’s own channel header, read 11 November 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.

Video runtime
24s
Average length
24s

Measured directly from 1 video 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 27 posts held from the last 30 days (7.41%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 21:48 UTC≈3,270 viewsread 11 November 2026

🚨 ALERTA | Web3Auth vació wallets vulnerables… para salvarlas Una vulnerabilidad en la infraestructura de Web3Auth expuso claves privadas de usuarios que entraban a Keplr con Google o Apple. 📍 Lo que pasó: 🔸 Según Bitquery, los hackers vaciaron más de 44.000 direcciones 🔸 Web3Auth retiró unos $5,6 millones de wallets vulnerables usando el mismo acceso 🔸 El objetivo: ponerlos a salvo antes que los atacantes Si usas…

10 Nov 2026, 21:46 UTC≈3,710 viewsread 11 November 2026
Photo

🚨 ALERTA | Hackeo a NEAR AI El 8 de noviembre un atacante explotó una vulnerabilidad en el motor SGLang, comprometió un servidor de IA de NEAR AI y desde allí accedió a otros sistemas internos. 📍 Impacto: 🔸 Unos 100 usuarios afectados 🔸 18 agentes de IA comprometidos 🔸 Investigación en curso Seguimos rastreando cada amenaza. Activa las notificaciones 🔔

8 Nov 2026, 17:43 UTC≈3,410 viewsread 11 November 2026
Photo

🚨 ALERTA | China va contra Solana El Banco Popular de China revisará a empresas y personas que promovieron Solana en el país. 📍 Qué pasó: 🔸 Un anuncio de Solana apareció en un rascacielos del distrito financiero de Shanghái 🔸 El regulador suspendió los eventos presenciales de Solana Accelerate China 2026 🔸 China mantiene la prohibición a la promoción de criptomonedas Rastreamos cada amenaza para que tú no seas la …

8 Nov 2026, 17:40 UTC≈3,500 viewsread 11 November 2026
Photo

🚨 ALERTA | Mercado Bitcoin: el daño sería mayor El exchange brasileño aseguró que había contenido el hackeo, pero según Bitquery el atacante siguió retirando fondos más de cinco horas. 📍 Cifras: 🔸 Analistas estiman el daño en $48,6 millones 🔸 La plataforma calcula $36,3 millones 🔸 Depósitos y retiros siguen suspendidos Seguimos rastreando cada movimiento. Activa las notificaciones 🔔

5 Nov 2026, 21:28 UTC≈3,150 viewsread 11 November 2026
Photo

🚨 ALERTA | Justin Sun acusa a World Liberty Financial Justin Sun acusó al proyecto cripto de la familia Trump de ocultar vínculos con los Emiratos Árabes Unidos y pidió sanciones judiciales. 📍 Contexto: 🔸 Sun demandó a WLFI después de que el proyecto congelara sus fondos 🔸 WLFI vendía tokens como empresa estadounidense 🔸 Tras la demanda, invocó a sus propietarios extranjeros para cuestionar la jurisdicción de EE.UU…

5 Nov 2026, 21:25 UTC≈3,210 viewsread 11 November 2026
Photo

🚨 ALERTA | ZachXBT identifica a la posible víctima del robo de $133 millones Según el detective on-chain, el dinero podría haberlo perdido el banco francés Crédit Mutuel Arkéa. 📍 Lo que sabemos: 🔸 Retiros sospechosos desde exchanges vinculados a una gran entidad financiera de Europa Occidental 🔸 El atacante ya lavó más de $30 millones 🔸 ZachXBT critica que la víctima haya guardado silencio Seguimos rastreando cada…

3 Nov 2026, 17:48 UTC≈3,120 viewsread 11 November 2026
Photo

Cómo trabaja Master Copy Traders: tres entradas y 40/40 No se trata de adivinar el movimiento, sino de ejecutar con estructura. Cada señal de XAUUSD se divide en tres posiciones: → la primera cierra en TP1 → la segunda se gestiona hacia TP2 → la tercera queda abierta para capturar la extensión El stop loss y el primer objetivo se mantienen a la misma distancia - 40 puntos - medidos desde tu entrada real, no desde …

3 Nov 2026, 17:09 UTC≈2,850 viewsread 11 November 2026
Photo

🚨 ALERTA | Robo de más de $133 millones a una empresa europea Según ZachXBT, una organización no identificada de la UE perdió más de $133 millones en cripto. 📍 Lo que sabemos: 🔸 El 1 de noviembre el atacante retiró USDC y USDT de varias cuentas en exchanges 🔸 Los fondos pasaron por Kraken, Crypto.com y OKX, que ya tomaron medidas 🔸 El hacker cambia el botín a ETH y Monero y lo mueve entre blockchains Rastreamos ca…

3 Nov 2026, 17:06 UTC≈3,140 viewsread 11 November 2026
Photo

🚨 ALERTA | Mercado Bitcoin hackeado por más de $40 millones El mayor exchange de Brasil confirmó un «incidente de seguridad» y suspendió temporalmente depósitos y retiros. 📍 Datos clave: 🔸 Hypernative detectó transferencias sospechosas por $40M+ 🔸 Los fondos se movieron a direcciones nuevas en Bitcoin, Ethereum, Solana, Tron, Polygon, Arbitrum, Avalanche, BNB Chain, Stellar y otras 🔸 El exchange asegura que los fon…

30 Oct 2026, 11:55 UTC≈3,530 viewsread 11 November 2026
Photo

🚨 ALERTA | Trezor Safe 5 con implante Un usuario de Indonesia encontró en su Trezor Safe 5 una placa adicional con módem celular. Según los primeros análisis, podía leer la frase semilla de la pantalla y enviarla a los atacantes. 📍 El dispositivo fue vendido por un revendedor no oficial. 🔸 Compra solo en tiendas oficiales 🔸 Revisa el hardware antes de usarlo Rastreamos cada amenaza para que tú no seas la próxima …

30 Oct 2026, 11:52 UTC≈3,820 viewsread 11 November 2026
Photo

🚨 ALERTA | Binance reserva $6.340 millones para cubrir el hackeo El exchange separó $6.340 millones para compensar a los usuarios afectados por el robo de $6.300 millones. 📍 Datos clave: 🔸 Los retiros deberían normalizarse en 45–48 horas 🔸 Binance coopera con el FBI y el Servicio Secreto de EE.UU. 🔸 Parte de los fondos ya fue congelada Seguimos rastreando cada movimiento. Activa las notificaciones 🔔 Foto: Bxalber…

28 Oct 2026, 17:17 UTC≈3,440 viewsread 11 November 2026
Photo

El fundador de eToro cree que la mayoría de las acciones de EE. UU. cotizarán 24/7 en 3–6 meses ⏰ Según Yoni Assia, sería un cambio enorme, parecido a cómo funciona hoy el mercado cripto. ♦️ Las acciones tokenizadas ya se negocian las 24 horas en varias plataformas Yo lo veo posible, pero el plazo de 3–6 meses me parece muy optimista. Foto: Vanja Savic / CC BY 4.0, Wikimedia Commons

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Crypto Tracker” (@TrakerCrypto), 9,353 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/TrakerCrypto.

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.