Telegram RegisterThe public register of Telegram
Telegram profile photo for CRT Wolf Trades🐺 📈💥

Channel

CRT Wolf Trades🐺 📈💥

@CRTModel

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

44subscribers

-2 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-1002425458114
TypeChannel
Username@CRTModel
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live9 October 2026
Measurements held4
Confirmed unchanged4 times, most recently 9 October 2026
On Telegramt.me/CRTModel

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 29 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

4446457 August 2026 — 46 subscribers10 August 2026 — 46 subscribers21 August 2026 — 45 subscribers7 September 2026 — 44 subscribers7 August 20267 September 2026
4 measurements spanning 31 days, net -2. 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 44–46 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 10:5644-1
21 Aug 2026, 11:5245-1
10 Aug 2026, 14:1646no change
7 Aug 2026, 14:4846first reading

Engagement

13 posts held, back to 29 May 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 13 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

9 Jun 2026, 09:10 UTC29 viewsread 10 August 2026

BUY XAUUSD NOW 4324 - 4329 TP1 4336 TP2 4338 TP3 4340 TP4 4342 TP5 open SL 4318

1 Jun 2026, 09:36 UTC40 viewsread 10 August 2026

Happy Monday guys...just sell EURUSD now NB...Swing Trade

29 May 2026, 13:47 UTC35 viewsread 10 August 2026
Photo

XAUUSD NASS100 GBPJPY ALL RUNNING IN DEEP PROFITS 📈 ✨️ ✅🔥🔥🐺 HAPPY FRIDAY GUYS!!

Showing the 12 most recent of 13 posts we hold for @CRTModel. 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 September 2026 — this entry's latest reading, not the date you are reading this.

“CRT Wolf Trades🐺 📈💥” (@CRTModel), 44 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/CRTModel.

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.