TYR-260929-99XPV2YY
RPLUSDT
-19.17% on margin
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.
- Stop1.92
- Entry1.95
- TP11.97
- TP21.98
- TP32.00
- TP42.01
- TP52.03
- TP62.04
Trade overview
Final return (% of margin)
Final return (% of margin): -19.17% (کاهش)Unleveraged price move (%)
-1.597% (کاهش)Leverage
12xHolding time
1h 39m- Signal entry price
- 1.95
- Entry trigger price
- 1.95
- Stop loss
- 1.92
- Implied exit price
- 1.92
- Observed exit price
- 1.92does not reconcile with the recorded return
- Exit reason
- Stop loss hit
- 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: 3165 · 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: 3169
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
- Loss
- Highest rung reached
- —
- Exit reason
- Stop loss hit
Modeled Result
Modeled- Final-exit ROI
- -19.17% (کاهش)
- Ladder ROI (highest rung)
- -19.17% (کاهش)
- ROI at published fractions
- -19.17% (کاهش)
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) | 1.95 | Database |
| Copy-trade requested entry | 1.95 | 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: 16 · Accepted: 2 · Failed: 14
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 · 1.95 | |
| Entry orders accepted by exchange | Exchange | exchange API accepted entry orders from 2 follower account(s); fill price not recorded | |
| Exchange entry fill | — | Exchange | Exchange execution data unavailable |
| Stop hit | DatabaseTelegram | position_events.SL_HIT — Telegram reply recorded · 1.92 · -19.17% (کاهش) | |
| Exit | Database | positions.closed_at, reason 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 | -19.1697 positions.pnl_percent_on_close | -19.1697 position_events[SL_HIT].roi_percent | 0.0000 | Reconciles |
| 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. | -19.1697 positions.pnl_percent_on_close | -18.4805 ROI(entry_price, closing event price_at_event) | -0.6892 | Flagged |
| Stored ROI ↔ ROI from observed exit price | -19.1697 positions.pnl_percent_on_close | -18.4805 ROI(entry_price, signal_quality_metrics.exit_price) | -0.6892 | Flagged |
| Ladder ROI ↔ independent recompute | -19.1697 positions.realized_pnl_pct | -19.1697 max(ROI highest rung reached, ROI recorded exit) | 0.0000 | Reconciles |
| Fraction-weighted ROI ↔ weighted legs | -19.1697 positions.laddered_pnl_pct | -19.1697 sum(frac * roi) over positions.pnl_legs | 0.0000 | Reconciles |
| TP event ROI ↔ published target no TP_HIT event to compare | در دسترس نیست TP_HIT roi_percent (worst rung) | در دسترس نیست ROI(entry_price, published TP price) | در دسترس نیست | Not comparable |
| Exchange ROI ↔ modelled ROI Exchange execution data unavailable | در دسترس نیست exchange realised ROI (net, on margin) | -19.1697 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 | 1.97 | Not filled | در دسترس نیست | not available | — |
| TP2 | 1.98 | Not filled | در دسترس نیست | not available | — |
| TP3 | 2.00 | Not filled | در دسترس نیست | not available | — |
| TP4 | 2.01 | Not filled | در دسترس نیست | not available | — |
| TP5 | 2.03 | Not filled | در دسترس نیست | not available | — |
| TP6 | 2.04 | 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 | 1.95 | در دسترس نیست | — | |
| SL_HIT | 1.92 | -19.17% (کاهش) | 3169 |
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, 144,321 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
6sSlippage
0.000%This trade is one of 1,585 published trades.