Telegram RegisterThe public register of Telegram
Telegram profile photo for Paradigm Trade Recaps

Channel

Paradigm Trade Recaps

@ParadigmTradeRecaps

On this record: Topic · Growth · Engagement · Posts · Cite this entry

453subscribers

-5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001489813020
TypeChannel
Username@ParadigmTradeRecaps
CreatedBetween 1 May 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/ParadigmTradeRecaps

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 21 September 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 why it has no browse page of its own yet.

Growth

451458454.57 August 2026 — 458 subscribers7 August 2026 — 458 subscribers7 August 2026 — 457 subscribers15 August 2026 — 455 subscribers22 August 2026 — 454 subscribers30 August 2026 — 453 subscribers7 September 2026 — 451 subscribers14 September 2026 — 452 subscribers7 October 2026 — 453 subscribers4537 August 20267 October 2026
9 measurements spanning 62 days, net -5. 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 450–459 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 18:58453+1
14 Sept 2026, 10:16452+1
7 Sept 2026, 17:17451-2
30 Aug 2026, 05:28453-1
22 Aug 2026, 13:59454-1
15 Aug 2026, 20:27455-2
7 Aug 2026, 19:44457-1
7 Aug 2026, 02:17458no change
7 Aug 2026, 02:07458first reading

Engagement

20 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 1 page 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 20 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Jul 2026, 06:35 UTC42 viewsread 7 August 2026

Trade: ETH Perpetual / ETH 31 Jul 26 Future Spread 500,000 USD @ 0.20 USD, Blocked on DBT (via Paradigm)

31 Jul 2026, 02:44 UTC46 viewsread 7 August 2026

Trade: BTC Perpetual / BTC 31 Jul 26 Future Spread 5,000,000 USD @ 0.00 USD, Blocked on DBT (via Paradigm)

31 Jul 2026, 02:40 UTC46 viewsread 7 August 2026

Trade: BTC Perpetual / BTC 31 Jul 26 Future Spread 2,000,000 USD @ 0.00 USD, Blocked on DBT (via Paradigm)

30 Jul 2026, 15:37 UTC50 viewsread 7 August 2026

Trade: BTC 25 Sep 26 30000 Put 100x (100 BTC) @ 0.0008 BTC, Vol 85.0%, Ref 64625.7700, Blocked on DBT (via Paradigm)

30 Jul 2026, 14:46 UTC50 viewsread 7 August 2026

Trade: ETH 28 Aug 26 2000 Call 1,000x (1,000 ETH) @ 0.0379 ETH, Vol 49.7% ETH 28 Aug 26 Future 713,108 USD @ 1,920 USD Blocked on DBT (via Paradigm)

30 Jul 2026, 13:30 UTC51 viewsread 7 August 2026

Trade: ETH 7 Aug 26 2000/2100 Call Spread 1,000x (2,000 ETH) @ 0.0089 ETH, Vols 50.0% 48.7%, Ref 1921.8100, Blocked on DBT (via Paradigm)

30 Jul 2026, 13:30 UTC48 viewsread 7 August 2026

Trade: ETH 7 Aug 26 2000/2100 Call Spread 1,000x (2,000 ETH) @ 0.009 ETH, Vols 50.1% 48.6%, Ref 1923.1000, Blocked on DBT (via Paradigm)

30 Jul 2026, 13:24 UTC40 viewsread 7 August 2026

Trade: ETH 7 Aug 26 2000/2100 Call Spread 1,000x (2,000 ETH) @ 0.009 ETH, Vols 49.9% 48.3%, Ref 1924.1500, Blocked on DBT (via Paradigm)

30 Jul 2026, 13:22 UTC40 viewsread 7 August 2026

Trade: ETH 7 Aug 26 2000/2100 Call Spread 1,000x (2,000 ETH) @ 0.0088 ETH, Vols 50.4% 48.6%, Ref 1921.8500, Blocked on DBT (via Paradigm)

30 Jul 2026, 13:19 UTC39 viewsread 7 August 2026

Trade: HYPE 28 Aug 26 100 Call 1x (1 HYPE) @ 0.001 USDC, Vol 93.7%, Ref 53.0062, Blocked on PRDX (via Paradigm)

30 Jul 2026, 13:19 UTC39 viewsread 7 August 2026

Trade: ETH 7 Aug 26 2000/2100 Call Spread 1,000x (2,000 ETH) @ 0.0088 ETH, Vols 50.5% 48.6%, Ref 1922.6600, Blocked on DBT (via Paradigm)

30 Jul 2026, 13:17 UTC39 viewsread 7 August 2026

Trade: ETH 7 Aug 26 2000/2100 Call Spread 1,000x (2,000 ETH) @ 0.0087 ETH, Vols 50.6% 48.5%, Ref 1922.2600, Blocked on DBT (via Paradigm)

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

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

“Paradigm Trade Recaps” (@ParadigmTradeRecaps), 453 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/ParadigmTradeRecaps.

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.