Skip to content
CRYPTO LIVE
$BTC$64,500.00+1.85%$ETH$2,550.00+2.40%$SOL$152.40+4.12%$BNB$582.10-0.45%$XRP$0.5840+1.15%$DOGE$0.1240+5.60%$ADA$0.3820-1.20%$AVAX$28.50+3.80%$LINK$11.60+2.10%$SUI$1.88+7.45%$PEPE$0.00000980+6.20%$NEAR$4.85-0.80%$BTC$64,500.00+1.85%$ETH$2,550.00+2.40%$SOL$152.40+4.12%$BNB$582.10-0.45%$XRP$0.5840+1.15%$DOGE$0.1240+5.60%$ADA$0.3820-1.20%$AVAX$28.50+3.80%$LINK$11.60+2.10%$SUI$1.88+7.45%$PEPE$0.00000980+6.20%$NEAR$4.85-0.80%
TradeDiscuss
Sign Up
AUDUSD▲ long4hlow conviction🔒 Locked at publish

Posted by mk_king44 · 2026-09-14 11:15:56 UTC

Live

The entry filled and the call is being tracked candle by candle.

✓ Timestamp recorded✓ Outcome checked— Identity verified— Broker-connected
Price against the levels5m candles
Entry 0.71298Stop 0.70230TP1 0.7308009-14 09:20 UTC09-14 14:55 UTC
Closes of the same stored candles the outcome was computed from, with the levels locked at publication. The shaded band is the distance to the stop — one R.
Levels — locked at publication
1
Entry
0.71298
platform quote
Stop
0.70230
−1.00R
TP1 · 100%
0.73080
+1.67R

What is the logic behind this AUDUSD long?

Written by the trader before the outcome was known, and never edited since.

Retesting key support at 0.713, high volume, liquidity sweep, invalidation below 0.7115.

Thesis at publication

The longer case, also locked at publication.

AUDUSD retesting key support at 0.7250, where prior buying interest was evident. Invalidates below 0.7230, where liquidity sweeps occurred.

Market context

What was true around AUDUSD when this call was published.

Price at post
0.71298
mid · ICMarketsSC-MT5-3
Price nowlive
0.71260
Move since post
-0.05%
In R terms
-0.04R
Relative to this call's own risk
Consensus when this was posted

There were no other open AUDUSD calls when this was published.

This trader's record at that moment

This was among their first calls — no graded record existed yet.

Discussion (2)

Comments do not affect this call's grade or the trader's performance figures.

Log in to join the discussion.

  1. mk_king44

    Nice entry, but could you clarify your invalidation level to manage risk effectively?

  2. gracetaylr

    Great entry at support! Confirm break for invalidation.