Channel

Cracked EA

@crackedEAfx

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

274subscribers

-6 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	-1001590390299
Type	Channel
Username	@crackedEAfx
Created	Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	8 August 2026
Last confirmed live	30 August 2026
Measurements held	5
Confirmed unchanged	1 time, most recently 30 August 2026
On Telegram	t.me/crackedEAfx

Growth

5 measurements spanning 23 days, net -6. 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 273–281 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
30 Aug 2026, 06:45	274	-3
22 Aug 2026, 12:07	277	-1
14 Aug 2026, 16:38	278	-2
8 Aug 2026, 08:33	280	no change
7 Aug 2026, 09:33	280	first reading

Engagement

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

Recent posts

11 Jan 2026, 14:55 UTC147 viewsread 8 August 2026

Photo

» NO Profit Sharing lifetime » Free EA/Robot lifetime » Free VPS lifetime* *S&K berlaku di sini Ping @luckymeeeeeeeeee / @tommya0702 for joining Ping @itsdwip for partnership/collaboration/CT Pelepasan tanggung jawab: Perdagangan derivatif memberikan tingkat risiko yang sangat tinggi terhadap modal Anda dan Anda hanya boleh melakukannya dengan sejumlah uang yang bisa Anda relakan untuk menanggung potensi kerugiann…

11 Jan 2026, 14:55 UTC127 viewsread 8 August 2026

Photo

20 Dec 2025, 17:27 UTC148 viewsread 8 August 2026

Photo

14 Dec 2025, 16:27 UTC134 viewsread 8 August 2026

Photo

7 Dec 2025, 16:48 UTC120 viewsread 8 August 2026

Photo

30 Nov 2025, 04:07 UTC122 viewsread 8 August 2026

Photo

24 Nov 2025, 19:32 UTC115 viewsread 8 August 2026

Photo

16 Nov 2025, 16:57 UTC122 viewsread 8 August 2026

Photo

9 Nov 2025, 06:18 UTC139 viewsread 8 August 2026

Photo

5 Nov 2025, 11:36 UTC122 viewsread 8 August 2026

Photo

28 May 2025, 15:54 UTC245 viewsread 8 August 2026

Photo

14 Dec 2024, 16:36 UTC375 viewsread 8 August 2026

Photo

Source: https://www.forexfactory.com/calendar GMT +7 Economic Calendar 101: https://www.babypips.com/news/economic-calendar-101 Disclaimer ON

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

“Cracked EA” (@crackedEAfx), 274 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/crackedEAfx.

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.