Skip to main content
TradeYarFutures market watch

TYR-260718-78QZAHZ8

JUPUSDT

-19.01% on margin

SHORTLoss15m

There is no dollar figure in this record: position size was never stored. The only unit available is percent.

Trade geometry

Stop, entry and the take-profit rungs

The prices recorded when the signal was sent. Rungs that actually filled are marked.

  • Stop0.1971
  • Entry0.1936
  • TP10.1884
  • TP20.1869
  • TP30.1854
  • TP40.1840
  • TP50.1825
  • TP60.1811

Trade overview

Final return (% of margin)

Final return (% of margin): -19.01% (کاهش)

Unleveraged price move (%)

-1.901% (کاهش)

Leverage

10x

Holding time

2h 38m
Signal entry price
0.1936
Entry trigger price
0.1936
Stop loss
0.1971
Implied exit price
0.1973
Observed exit price
0.1976does not reconcile with the recorded return
Exit reason
SL
Signal created
Activated
Closed

observed_exit_price is the market price seen when the exit condition was detected. The recorded ROI is booked at a modelled stop fill of sl +/- 0.10%, so on stop exits the two do not match. Aggregates use the recorded ROI only.

Proof it was published before the outcome

No Telegram message id is recorded for this trade. That means we cannot prove pre-publication for this particular trade — and we do not hide it.

The signal's original message was posted to the channel before the outcome existed; the message id and the follow-up replies (a TP or SL hit) are stored in this same record.

Take-profit ladder

This trade's six take-profit rungs and which of them actually filled. An unfilled rung is «not filled», not zero.

Take-profit ladder
RungTarget priceFilledReturn at fillFilled atTelegram reply
TP10.1884Not filledدر دسترس نیستnot available
TP20.1869Not filledدر دسترس نیستnot available
TP30.1854Not filledدر دسترس نیستnot available
TP40.1840Not filledدر دسترس نیستnot available
TP50.1825Not filledدر دسترس نیستnot available
TP60.1811Not filledدر دسترس نیستnot available

Partial closes

No partial close was recorded for this trade.

Event timeline

Times are shown in UTC; hover a timestamp to see the same instant in Tehran local time. The machine value in each `datetime` attribute is always UTC.

Event timeline
EventTimePriceReturn at that momentTelegram reply
ENTRY_TRIGGERED0.1936در دسترس نیست
SL_HIT0.1976-19.01% (کاهش)

Timeline consistency check: Consistent

Every timestamp on this page is UTC. position_events.occurred_at is stored naive in Asia/Tehran local time and is converted here. The event log is written by the monitor loop immediately after it stamps positions.closed_at, so a closing event can trail the close by a few seconds; measured across the whole ledger on 2026-08-15, 31 of 14,568 events did, the worst by 125s and none before its position opened. Every such event is listed above with no tolerance applied; the 300s tolerance only decides whether this trade is flagged as inconsistent.

Execution quality

Entry latency

7s

Slippage

0.000%

This trade is one of 1,156 published trades.