Telegram RegisterThe public register of Telegram
Telegram profile photo for Trade Intelligence Club 📈

Channel

Trade Intelligence Club 📈

@camilafxclub

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

8,840subscribers

-1,760 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-1003209686713
TypeChannel
Username@camilafxclub
Description💎 Tu resultado depende de tu disciplina. Sigue todas las actualizaciones del trader. ✅ Señales Buy/Sell en tiempo real ✅ Entrada, Stop Loss y Take Profit ✅ Seguimiento de posiciones ✅ Gestión del riesgo 📩 Soporte y consultas: https://t.me/camilaortegaa
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/camilafxclub

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 10 August 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. This entry also forms a group of 2 channels linked by matching posts. 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
@camilafxclub/197 · this entry4 Aug 2026, 16:12 UTC@camilafxclub2/2004 Aug 2026, 16:12 UTC1.00under a minute
@camilafxclub/200 · this entry5 Aug 2026, 14:25 UTC@camilafxclub2/2045 Aug 2026, 14:25 UTC1.00under a minute
@camilafxclub/202 · this entry6 Aug 2026, 12:26 UTC@camilafxclub2/2096 Aug 2026, 16:26 UTC1.004.0 hours
@camilafxclub/204 · this entry9 Aug 2026, 10:13 UTC@camilafxclub2/2139 Aug 2026, 10:13 UTC1.00under a minute
@camilafxclub/207 · this entry9 Aug 2026, 16:39 UTC@camilafxclub2/2169 Aug 2026, 16:39 UTC1.00under a minute
@camilafxclub/210 · this entry10 Aug 2026, 11:42 UTC@camilafxclub2/22110 Aug 2026, 15:41 UTC1.004.0 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
@camilafxclub215 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–7)

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. 2 of the 7 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 21 comparable posts for this entry, running 31 July 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 2 channels, the one whose matching posts we hold earliest is @camilafxclub2. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, 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 2 registered channels linked by matching posts. 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

8,84010,6009,7207 August 2026 — 10,600 subscribers8 August 2026 — 10,593 subscribers8 August 2026 — 10,566 subscribers9 August 2026 — 10,558 subscribers11 August 2026 — 10,514 subscribers12 August 2026 — 10,501 subscribers13 August 2026 — 10,489 subscribers14 August 2026 — 10,479 subscribers15 August 2026 — 10,463 subscribers17 August 2026 — 10,432 subscribers18 August 2026 — 10,425 subscribers19 August 2026 — 10,413 subscribers20 August 2026 — 10,396 subscribers21 August 2026 — 10,387 subscribers22 August 2026 — 10,366 subscribers24 August 2026 — 10,310 subscribers25 August 2026 — 10,303 subscribers26 August 2026 — 10,286 subscribers27 August 2026 — 10,274 subscribers28 August 2026 — 10,264 subscribers29 August 2026 — 10,254 subscribers30 August 2026 — 10,250 subscribers31 August 2026 — 10,239 subscribers1 September 2026 — 10,234 subscribers2 September 2026 — 10,225 subscribers3 September 2026 — 10,209 subscribers5 September 2026 — 10,203 subscribers8 September 2026 — 10,183 subscribers11 September 2026 — 10,107 subscribers13 September 2026 — 10,071 subscribers14 September 2026 — 10,061 subscribers16 September 2026 — 10,056 subscribers18 September 2026 — 10,040 subscribers25 September 2026 — 9,975 subscribers4 October 2026 — 9,820 subscribers10 October 2026 — 9,705 subscribers14 October 2026 — 9,673 subscribers17 October 2026 — 9,637 subscribers20 October 2026 — 9,590 subscribers23 October 2026 — 9,502 subscribers26 October 2026 — 9,436 subscribers29 October 2026 — 9,362 subscribers1 November 2026 — 9,274 subscribers3 November 2026 — 9,143 subscribers7 November 2026 — 9,048 subscribers10 November 2026 — 8,948 subscribers15 November 2026 — 8,840 subscribers7 August 202615 November 2026
47 measurements spanning 100 days, net -1,760. 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,576–10,864 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
15 Nov 2026, 21:518,840-108
10 Nov 2026, 13:518,948-100
7 Nov 2026, 03:589,048-95
3 Nov 2026, 19:549,143-131
1 Nov 2026, 04:589,274-88
29 Oct 2026, 10:469,362-74
26 Oct 2026, 06:279,436-66
23 Oct 2026, 06:509,502-88
20 Oct 2026, 00:309,590-47
17 Oct 2026, 00:459,637-36
14 Oct 2026, 07:409,673-32
10 Oct 2026, 19:599,705-115
4 Oct 2026, 20:209,820-155
25 Sept 2026, 12:159,975-65
18 Sept 2026, 22:1710,040-16
16 Sept 2026, 15:2010,056-5
14 Sept 2026, 16:1710,061-10
13 Sept 2026, 01:5910,071-36
11 Sept 2026, 06:1710,107-76
8 Sept 2026, 08:5910,183first reading

Engagement

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

What this channel posts

Photos
147
Videos
3
Links
5

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

Video runtime
4m 19s
Average length
1m 26s

Measured directly from 3 videos 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

12 Aug 2026, 15:06 UTC37 viewsread 18 November 2026
Video

📢📢📢📢📢📢 Aquí les dejo mi análisis de una situación muy interesante! El par Euro/Dólar está demostrando fuerza 🚀 En este momento rebotamos en otra de las zonas marcadas en rojo❗️ Pienso que volveremos a consolidar entre zonas y luego iremos a buscar la zona roja, apuntando al 1.15772 📈

11 Aug 2026, 14:22 UTC28 viewsread 18 November 2026
Photo

Os dejo por aquí un resumen superrápido de lo que esperamos para estos días en el mercado 🚀 Como os explico en el vídeo, se vienen horas clave con los datos de inflación (IPC) y PPI en USA, así que mucha atención a los niveles: ❤️ Oro (XAU/USD): Tras el impulso brutal por encima de los 4.260$, no perseguimos el precio arriba. Esperamos un retroceso sano a la zona de 4.210$– 4.225$ para buscar entradas en compras co…

11 Aug 2026, 13:26 UTC17 viewsread 18 November 2026
Photo

Cómo van las cosas, mi gente? Ni piensen que ando descansando sin hacer nada! Les estoy preparando un análisis de mercado monstruoso 🔥 Solo lo más importante y nada de adivinanzas, sino basado en un montón de factores, colegas! En fin, si quieren operar en serio, ¡se ven el análisis y nos le metemos con toda al mercado! 💥 🟢 Esperamos la reseña...

10 Aug 2026, 11:42 UTC14 viewsread 18 November 2026
Video

✔️ Miren todos pues! Les explico el análisis técnico de una, rápido y sin rodeos! Te lo mostraré con más detalle por mensaje privado 🚀

10 Aug 2026, 11:35 UTC13 viewsread 18 November 2026

💸 Quieren un escenario rápido de cómo se va a mover el oro (XAU/USD)? 😎 Ya le estoy echando un ojo al gráfico y veo un movimiento re interesante que no puedo dejar de compartirles ;)

9 Aug 2026, 16:39 UTC15 viewsread 18 November 2026
Video

📢📢📢📢📢📢 EUR/USD El mensaje se dio tal cual, parce! Leímos el gráfico como era. Si entraron a la operación, mándenme sus capturas de pantalla 🚀 Me interesa mucho ver sus comentarios y opiniones 😍 Esperamos al lunes y miramos para dónde coge el euro!

9 Aug 2026, 10:13 UTC12 viewsread 18 November 2026
Photo

Hola chicos! 👋 Os dejo un resumen superrápido de lo que está pasando con Bitcoin (BTC) para cerrar la semana 📊 Ayer rozamos máximos de agosto cerca de los 65.300$. El detonante principal fue el informe de empleo de USA (los datos de las NFP y el desempleo salieron más flojos de lo esperado), lo que vuelve a avivar las expectativas de que la Reserva Federal recortará los tipos de interés bastante pronto. 🎯 Qué esto…

7 Aug 2026, 12:58 UTC14 viewsread 18 November 2026
Photo

🙋😴😴😊 Fijaos en el gráfico, chicas y chicos! El EUR/USD está haciendo exactamente lo que os marqué en el canal, paso por paso y sin salirse ni un milímetro de la ruta 🎯 Ahora mismo cotizamos sobre los 1.1526, y si os fijáis en el rectángulo que os dibujé, el precio está respetando la estructura al dedillo: ✅ Punto 1 (Subida inicial): Tuvimos un impulso limpio desde los 1.1500 hasta buscar la zona alta en 1.1560. …

6 Aug 2026, 12:26 UTC12 viewsread 18 November 2026
Photo

Actualización rápida de los pares con el dólar (EUR/USD y GBP/USD) ante los datos de hoy 💵 💵 EUR/USD Situación actual: El par cotiza ahora mismo en la zona de los 1.1538 - 1.1540, manteniendo la estructura alcista tras rebotar limpio desde la zona de demanda. Escenario alcista (Long ⬆️): Si los datos de desempleo de EE.UU. salen flojos, el dólar perderá terreno y el EUR/USD buscará romper con fuerza la resistencia…

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

Posts edited after publishing

@camilafxclub edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
12 August 2026

Mentions

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

“Trade Intelligence Club 📈” (@camilafxclub), 8,840 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/camilafxclub.

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.