Skip to main content
TradeYarFutures market watch
فارسیJoin VIP

TYR-260616-9SHSF4P6

GMTUSDT

+32.38% on margin

The price reached a target and a “TP hit” card was published, but no rung was booked; the return above assumes the whole position was held to the exit.

SHORTRungs, then exited green15mPre-announced

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

Open the original Telegram message

Trade geometry

Stop, entry and the take-profit rungs

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

  • Stop0.008279
  • Entry0.008430
  • TP10.008203
  • TP20.008139
  • TP30.008075
  • TP40.008011
  • TP50.007948
  • TP60.007884

Trade overview

Final return (% of margin)

Final return (% of margin): +32.38% (افزایش)

Unleveraged price move (%)

+2.699% (افزایش)

Leverage

12x

Holding time

2h 57m
Signal entry price
0.008430
Entry trigger price
0.008430
Stop loss
0.008279
Implied exit price
0.008203
Observed exit price
0.008280does not reconcile with the recorded return
Exit reason
Trailing stop
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

This signal was posted to the Telegram channel before the outcome existed, and the message id is stored in this record.

Open the original Telegram message

Message id: 21594 · Channel id: -1002724500048

This link points at the private signal channel and opens only for members of it. The message id and channel id are published here so that any member can check this record against the original message.

Recorded reply ids under the original message: 21612، 21615

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.

Transparency & Verification for this trade

Modeled

Signal Result

Database
Result
Win
Highest rung reached
TP1
Exit reason
Trailing stop

Modeled Result

Modeled
Final-exit ROI
+20.30% (افزایش)
Ladder ROI (highest rung)
+32.38% (افزایش)
ROI at published fractions
+23.32% (افزایش)

No fees or funding, % of margin

Exchange-Verified Result

Unavailable

Exchange execution data unavailable

Execution verification

Exchange execution data unavailable

Execution verification
FieldValueSource
ExchangeExchange execution data unavailableExchange
Exchange order idExchange execution data unavailableExchange
Entry / exit sizeExchange execution data unavailableExchange
Requested entry (signal)0.008430Database
Actual average entry fillExchange execution data unavailableExchange
Actual exit fillExchange execution data unavailableExchange
Entry fill timeExchange execution data unavailableExchange
Exit fill timeExchange execution data unavailableExchange
Entry slippage (exchange)Exchange execution data unavailableExchange
Trigger vs signal slippage (price feed, not exchange)0.000%Database
FeesExchange execution data unavailableExchange
FundingExchange execution data unavailableExchange
Realized PnL (USDT)Exchange execution data unavailableExchange
Realized ROIExchange execution data unavailableExchange

Copy-trade order evidence Exchange

How many follower accounts had an entry order for this signal accepted by the exchange. It proves the order reached the exchange; its fill price, fee and PnL were not stored and are used in no figure.

Signalled: 4 · Accepted: 0 · Failed: 4

Timeline with the source of every step

Timeline with the source of every step
StepTimeSourceDetail
Signal createdDatabasepositions.created_at
Published to TelegramTelegramTelegram message id stored with the record; time is signal_quality_metrics.dispatched_at
Entry (price feed)Databasepositions.activated_at — the price feed reached the entry; the fill is modelled at the signal entry price · 0.008430
Exchange entry fill—ExchangeExchange execution data unavailable
TP1 hitDatabaseTelegramposition_events.TP_HIT — Telegram reply recorded · 0.008203 · +32.38% (افزایش)
Stop hitDatabaseTelegramposition_events.SL_HIT — Telegram reply recorded · 0.008280 · +20.30% (افزایش)
ExitDatabasepositions.closed_at, reason TRAILING_SL
Exchange exit fill—ExchangeExchange execution data unavailable
Modelled PnLModeledrecorded / ladder / laddered ROI on margin, no fees or funding
Exchange-verified PnL—ExchangeExchange execution data unavailable

PnL reconciliation

Flagged

Tolerance (ROI points): 0.5

PnL reconciliation
CheckValue 1Value 2DeltaStatus
Stored ROI ↔ closing-event ROI+20.2958

positions.pnl_percent_on_close

+20.2958

position_events[SL_HIT].roi_percent

0.0000Reconciles
Stored ROI ↔ ROI from exit-event price

Within the modelled stop band: stop exits are booked at sl +/- 0.10 %, i.e. up to 1.20 ROI points at 12x.

+20.2958

positions.pnl_percent_on_close

+21.3523

ROI(entry_price, closing event price_at_event)

-1.0565Flagged
Stored ROI ↔ ROI from observed exit price+20.2958

positions.pnl_percent_on_close

+21.3523

ROI(entry_price, signal_quality_metrics.exit_price)

-1.0565Flagged
Ladder ROI ↔ independent recompute+32.3843

positions.realized_pnl_pct

+32.3843

max(ROI highest rung reached, ROI recorded exit)

0.0000Reconciles
Fraction-weighted ROI ↔ weighted legs+23.3179

positions.laddered_pnl_pct

+23.3179

sum(frac * roi) over positions.pnl_legs

0.0000Reconciles
TP event ROI ↔ published target

1 rung event(s) compared; delta is the largest deviation

0.0000

TP_HIT roi_percent (worst rung)

0.0000

ROI(entry_price, published TP price)

0.0000Reconciles
Exchange ROI ↔ modelled ROI

Exchange execution data unavailable

در دسترس نیست

exchange realised ROI (net, on margin)

+20.2958

positions.pnl_percent_on_close

در دسترس نیستNo exchange data
Exchange fees and funding

Exchange execution data unavailable

در دسترس نیست

exchange fees

در دسترس نیست

exchange funding

در دسترس نیستNo exchange data

Transparency & Verification page

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.008203Filled+32.38% (افزایش)21612
TP20.008139Not filledدر دسترس نیستnot available—
TP30.008075Not filledدر دسترس نیستnot available—
TP40.008011Not filledدر دسترس نیستnot available—
TP50.007948Not filledدر دسترس نیستnot available—
TP60.007884Not 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.008430در دسترس نیست—
SL_ADJUSTED0.008400در دسترس نیست—
TP_HIT TP10.008203+32.38% (افزایش)21612
SL_ADJUSTED0.008342در دسترس نیست—
SL_ADJUSTED0.008308در دسترس نیست—
SL_ADJUSTED0.008280در دسترس نیست—
SL_ADJUSTED0.008279در دسترس نیست—
SL_ADJUSTED0.008279در دسترس نیست—
SL_ADJUSTED0.008279در دسترس نیست—
SL_HIT0.008280+20.30% (افزایش)21615

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 this snapshot, 146,719 timestamped events, 1 before the position opened, 41 after it closed across 39 position(s), the worst by 125s. 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

2s

Slippage

0.000%

This trade is one of 1,595 published trades.