TYR-260710-JW4MKOO0
ARBUSDT
+6.05% 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.
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.0910
- Entry0.0905
- TP10.0907
- TP20.0911
- TP30.0915
- TP40.0919
- TP50.0922
- TP60.0927
Trade overview
Final return (% of margin)
Final return (% of margin): +6.05% (افزایش)Unleveraged price move (%)
+0.504% (افزایش)Leverage
12xHolding time
18 min- Signal entry price
- 0.0905
- Entry trigger price
- 0.0905
- Stop loss
- 0.0910
- Implied exit price
- 0.0909
- Observed exit price
- 0.0908does 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: 502 · Channel id: -1004290234404
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: 504، 505
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
ModeledSignal Result
Database- Result
- Win
- Highest rung reached
- TP1
- Exit reason
- Trailing stop
Modeled Result
Modeled- Final-exit ROI
- +6.05% (افزایش)
- Ladder ROI (highest rung)
- +6.05% (افزایش)
- ROI at published fractions
- +5.36% (افزایش)
No fees or funding, % of margin
Exchange-Verified Result
UnavailableExchange execution data unavailable
Execution verification
Exchange execution data unavailable
| Field | Value | Source |
|---|---|---|
| Exchange | Exchange execution data unavailable | Exchange |
| Exchange order id | Exchange execution data unavailable | Exchange |
| Entry / exit size | Exchange execution data unavailable | Exchange |
| Requested entry (signal) | 0.0905 | Database |
| Copy-trade requested entry | 0.0905 | Exchange |
| Actual average entry fill | Exchange execution data unavailable | Exchange |
| Actual exit fill | Exchange execution data unavailable | Exchange |
| Entry fill time | Exchange execution data unavailable | Exchange |
| Exit fill time | Exchange execution data unavailable | Exchange |
| Entry slippage (exchange) | Exchange execution data unavailable | Exchange |
| Trigger vs signal slippage (price feed, not exchange) | 0.000% | Database |
| Fees | Exchange execution data unavailable | Exchange |
| Funding | Exchange execution data unavailable | Exchange |
| Realized PnL (USDT) | Exchange execution data unavailable | Exchange |
| Realized ROI | Exchange execution data unavailable | Exchange |
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: 8 · Accepted: 1 · Failed: 7
Timeline with the source of every step
| Step | Time | Source | Detail |
|---|---|---|---|
| Signal created | Database | positions.created_at | |
| Published to Telegram | Telegram | Telegram message id stored with the record; time is signal_quality_metrics.dispatched_at | |
| Entry (price feed) | Database | positions.activated_at — the price feed reached the entry; the fill is modelled at the signal entry price · 0.0905 | |
| Entry orders accepted by exchange | Exchange | exchange API accepted entry orders from 1 follower account(s); fill price not recorded | |
| Exchange entry fill | — | Exchange | Exchange execution data unavailable |
| TP1 hit | DatabaseTelegram | position_events.TP_HIT — Telegram reply recorded · 0.0907 · +3.32% (افزایش) | |
| Stop hit | DatabaseTelegram | position_events.SL_HIT — Telegram reply recorded · 0.0908 · +6.05% (افزایش) | |
| Exit | Database | positions.closed_at, reason TRAILING_SL | |
| Exchange exit fill | — | Exchange | Exchange execution data unavailable |
| Modelled PnL | Modeled | recorded / ladder / laddered ROI on margin, no fees or funding | |
| Exchange-verified PnL | — | Exchange | Exchange execution data unavailable |
PnL reconciliation
FlaggedTolerance (ROI points): 0.5
| Check | Value 1 | Value 2 | Delta | Status |
|---|---|---|---|---|
| Stored ROI ↔ closing-event ROI | +6.0462 positions.pnl_percent_on_close | +6.0462 position_events[SL_HIT].roi_percent | 0.0000 | Reconciles |
| Stored ROI ↔ ROI from exit-event price The stored ROI is 2.20 ROI points MORE favourable than the price recorded at the exit, beyond the 1.20-point modelled stop band: the stored result books the stop level while the market had already moved past it. | +6.0462 positions.pnl_percent_on_close | +3.8470 ROI(entry_price, closing event price_at_event) | +2.1992 | Flagged |
| Stored ROI ↔ ROI from observed exit price | +6.0462 positions.pnl_percent_on_close | +3.8470 ROI(entry_price, signal_quality_metrics.exit_price) | +2.1992 | Flagged |
| Ladder ROI ↔ independent recompute | +6.0462 positions.realized_pnl_pct | +6.0462 max(ROI highest rung reached, ROI recorded exit) | 0.0000 | Reconciles |
| Fraction-weighted ROI ↔ weighted legs | +5.3638 positions.laddered_pnl_pct | +5.3638 sum(frac * roi) over positions.pnl_legs | 0.0000 | Reconciles |
| 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.0000 | Reconciles |
| Exchange ROI ↔ modelled ROI Exchange execution data unavailable | در دسترس نیست exchange realised ROI (net, on margin) | +6.0462 positions.pnl_percent_on_close | در دسترس نیست | No exchange data |
| Exchange fees and funding Exchange execution data unavailable | در دسترس نیست exchange fees | در دسترس نیست exchange funding | در دسترس نیست | No exchange data |
Take-profit ladder
This trade's six take-profit rungs and which of them actually filled. An unfilled rung is «not filled», not zero.
| Rung | Target price | Filled | Return at fill | Filled at | Telegram reply |
|---|---|---|---|---|---|
| TP1 | 0.0907 | Filled | +3.32% (افزایش) | 504 | |
| TP2 | 0.0911 | Not filled | در دسترس نیست | not available | — |
| TP3 | 0.0915 | Not filled | در دسترس نیست | not available | — |
| TP4 | 0.0919 | Not filled | در دسترس نیست | not available | — |
| TP5 | 0.0922 | Not filled | در دسترس نیست | not available | — |
| TP6 | 0.0927 | Not 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 | Time | Price | Return at that moment | Telegram reply |
|---|---|---|---|---|
| ENTRY_TRIGGERED | 0.0905 | در دسترس نیست | — | |
| TP_HIT TP1 | 0.0907 | +3.32% (افزایش) | 504 | |
| SL_HIT | 0.0908 | +6.05% (افزایش) | 505 |
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,761 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
0sSlippage
0.000%This trade is one of 1,603 published trades.