Channel
@SignalSemperCrypto
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
244subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001410978106 |
|---|---|
| Type | Channel |
| Username | @SignalSemperCrypto |
| Description | Canal Oficial de SemperCrypto® para la investigación, análisis y proyecciones de criptomonedas para Exchange (Bitmex-Binance)💰 Garantizamos 10-50% P&L o más diario en el VIP Para consultas sobre nuestro servicios VIP Póngase en Contacto: @SemperCrypto |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/SignalSemperCrypto |
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 100% 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.
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.
Posts published here appear word for word 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @SignalSemperCrypto/5651 · this entry14 Jun 2024, 16:43 UTC | @CryptoLionSignals/79814 Jun 2024, 16:43 UTC | 1.00 | under a minute |
| @CryptoLionSignals/80014 Jun 2024, 16:59 UTC | @SignalSemperCrypto/5653 · this entry14 Jun 2024, 16:59 UTC | 1.00 | under a minute |
| @SignalSemperCrypto/5654 · this entry24 Jun 2024, 01:30 UTC | @CryptoLionSignals/80124 Jun 2024, 01:30 UTC | 1.00 | under a minute |
| @SignalSemperCrypto/5657 · this entry26 Jun 2024, 20:46 UTC | @CryptoLionSignals/80426 Jun 2024, 20:46 UTC | 1.00 | under a minute |
| @SignalSemperCrypto/5659 · this entry5 Jul 2024, 04:19 UTC | @CryptoLionSignals/8065 Jul 2024, 04:20 UTC | 1.00 | under a minute |
| @SignalSemperCrypto/5662 · this entry5 Aug 2024, 12:50 UTC | @CryptoLionSignals/8095 Aug 2024, 12:50 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @CryptoLionSignals | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (15–2) |
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. None of the 2 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 20 May 2024 to 15 November 2024. 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.
Across the whole group of 2, the earliest publisher we hold is @SignalSemperCrypto — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 02:31 | 244 | no change |
| 6 Aug 2026, 16:50 | 244 | first reading |
18 posts held, back to 20 May 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 18 posts for this entry, the most recent from 15 November 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 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.
Bueno chicos en cuanto a #BTC el plan es aguantar lo que tenemos puede tener un ligero retroceso a la zonas de los ptos fibos que marco pero en general veo mucha fuerza alcista asi q como mucho capaz 0.382 serian los 83K pero de ahi para arriba el próximo punto son los 100K sin duda.
Otra cosa que quiero decirles que en estos momentos para HOLD no es un análisis para deshacerse del mercado sino para ir posicionándose incluso en los proyectos importantes que nosotros tenemos. Osea en #BTC, y nuestros proyectos cryptos importantes, como en mi caso: #ETH, #BNB, #RON, #LINK, #ROSE, #SOL
Bueno chicos en cuanto a #BTC vemos que quebró los 0.618 (52K) y esta tratando de tocar los 0.707 (48K) es muy probable que incluso llegue a nuestro target final seria los 0.786 (45K) nuestro análisis a pesar de el rebote de subida seguíamos firmes en el mercado porque no veíamos un patron que fuera propio para que todo cambiara, nuestro panorama aun sigue siendo bajista aun la economía mundial sigue en contracción c…
Bueno chicos como veníamos diciendo, ahora estamos en el 0.5 fibo en #BTC recuerden que son compras para HOLD así que son momentos donde el mercado esta en vision a 3-5 meses estas compras van a dar resultado.. por el momento todavía queda desarrollo de bajada, aunque pudiera haber una especie de rebote pequeño pero la idea sigue igual bajada por lo menos a los 50K-48K
Así como vamos posicionándose en #BTC, también en proyectos cryptos importantes, como en mi caso: #ETH, #BNB, #RON, #LINK, #ROSE, #SOL
Buenas chicos como vengo diciendo puntos en consideración los a partir de ahora se empieza hacer DCA (Dollar Cost Averaging) estamos en el 0.382 fibo en #BTC como vengo diciendo se van comprando y posicionándose en mercado en el 0.382, 0.5, 0.618, 0.707, 0.786 se los marco en la imagen, Esto son posicionamientos a largo plazo.
En comparación a otros momentos en TF semanales quieros mostrarles los momentos en que estamos en el RSI con los puntos rojos son los puntos donde estamos actualmente y cuando estuvimos en Abril-Mayo 2021 donde el precio tuvo su retroceso fuerte. Los puntos verde fueron la zona de compra.
Otro punto a considerar es que pase el tiempo y el precio no baje sino que haga un rango por la parte alta aprox de 20%-24% y pase el tiempo y el indicador se desarrolle y estemos ya en zonas de sobreventa RSI o en el mometum estemos por debajo del pto 23, y ahi si compramos porque el mercado si subiria pero comprar ahora es un riesgo porque todavía existe el riesgo de caída.
Buenas Chicos el mercado sigue todavía nuestro plan de proyección, ptos FIBOS de retrocesos a considerar... 0.382, 0.5, 0.618, 0.786, esas son zonas donde debemos tener fuertes puntos de compra. Esto es en el caso del retroceso y el indicador se desarrolle.
ahi le marco el recorrido que le falta al indicador RSI asi que sigue en el mismo plan de bajada en TF semanales.
Buenas chicos el mercado todavía sigue con la proyección de no subir, mi idea es que el mercado tenga un retroceso o en el mejor de los casos haga una tendencia lateral, mi idea sigue vigente, de hecho puede subir a valores como 70K tranquilamente yo hablo de que no va ver mucho movimientos alcista fuerte q nos vayamos a 80K no lo veo aun por lo menos dentro de 2 a 3 meses aproximadamente... por el contrario el riesg…
También les comparto el TOTAL que es la capitalización del mercado crypto es muy probable que haya retiros y tomas de ganancias de ciertas ballenas con lo cual hagan hundir el precio de ciertos activos cryptos.
Showing the 12 most recent of 18 posts we hold for @SignalSemperCrypto. 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 — 490,520 of 1,151,006entries 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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Señales SemperCrypto® 🦁” (@SignalSemperCrypto), 244 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/SignalSemperCrypto.
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.