TYR-260824-NA0JNQR4
LTCUSDT
+13.07% 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.
- Stop52.51
- Entry53.31
- TP153.89
- TP254.18
- TP354.51
- TP454.83
- TP555.20
- TP655.63
Trade overview
Final return (% of margin)
Final return (% of margin): +13.07% (افزایش)Unleveraged price move (%)
+1.089% (افزایش)Leverage
12xHolding time
4h 11m- Signal entry price
- 53.31
- Entry trigger price
- 53.31
- Stop loss
- 52.51
- Implied exit price
- 53.89
- Observed exit price
- 52.23does 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: 1828 · 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: 1829، 1843
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.
| Rung | Target price | Filled | Return at fill | Filled at | Telegram reply |
|---|---|---|---|---|---|
| TP1 | 53.89 | Filled | +13.07% (افزایش) | 1829 | |
| TP2 | 54.18 | Not filled | در دسترس نیست | not available | — |
| TP3 | 54.51 | Not filled | در دسترس نیست | not available | — |
| TP4 | 54.83 | Not filled | در دسترس نیست | not available | — |
| TP5 | 55.20 | Not filled | در دسترس نیست | not available | — |
| TP6 | 55.63 | 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 | 53.31 | در دسترس نیست | — | |
| PARTIAL_CLOSE_FAILED TP1 | 54.07 | در دسترس نیست | — | |
| TP_HIT TP1 | 53.89 | +13.07% (افزایش) | 1829 | |
| SL_HIT | 52.23 | -19.18% (کاهش) | 1843 |
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, 33,355 timestamped events, none before the position opened, 36 after it closed across 33 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,292 published trades.