Verified Trading Signals

MQL5 Signals: proof scope and population coverage

Identify the actual copied account: source-specific evidence questions for MQL5 Signals, not a completed paid-account test.

Editorial revision: 14 October 2026

Account copying. A documentation-based note, not a measured performance ranking.

Verification methods and user-led checklists. No provider has been certified by this site; declared coverage counts are not independently checked.

Account copying

Account-copy records can show executions but still need original-account, subscriber and cost scope.

Evidence still needed

Request original bytes, serialization version, proof file, verified attestation, complete signal-ID population, amendments and the separate execution ledger. A hash match is only one part of that request.

Assessment boundary

No paid-account test, complete trade population or independent execution comparison was supplied for this entry. Current terms, regional eligibility and the exact purchased offer require direct confirmation. No rating, rank or consumer-review count is asserted.

Source documents

Documentation establishes the stated mechanism, not tested trading performance. Checked 9 October 2026; a later version can differ.

Identify the actual copied account

Request source-account identity, continuous review period, purchased access, subscriber settings and original account records. Platform documentation is not a complete verification of every listed source. Keep source results, research displays and subscriber executions distinct. No account-copy subscription, proof population or broker ledger has been independently inspected here.

Reconcile copying differences

A subscriber can have different available instruments, quantities, funding and execution timing. Ask for source-to-subscriber order/fill mapping and costs rather than assigning the source account's return to every customer. Missing joins stay unresolved. A technical copy log can support operational inspection while full net account accounting and suitability remain separate questions.

An invented source-to-subscriber join

Use fictional source instruction SRC8 and subscriber account label SUB2. The source table contains one closed position, while SUB2 has two partial order labels and no complete fill export. A source position count cannot decide how much the subscriber executed or whether the two order labels concern the same original instruction. Request the stable mapping rather than applying the source result directly to the customer.

Suppose the subscriber also has an unavailable instrument mapping and a later cancellation record. Those are separate operational questions. They do not prove a failure or loss, but they prevent a complete execution reconstruction. A proof identifying the source message cannot supply the missing filled quantities, fees or cash-flow accounting. A correctly joined message history and a correctly reconciled account path are distinct achievements.

Retain source_account_id, source_instruction_id, original_version, subscriber_account_scope, instrument_mapping_version, copy_settings, order_id, filled_quantity_source, fee_scope and account_statement_identity. The example has no actual account credentials, broker execution or provider proof. A paid-platform inspection would have to use genuine lawful records and current account settings. The bounded result is unresolved source-to-subscriber execution lineage, not an empirically measured copy-trading return or a personalized suitability verdict. A platform help page establishes where to begin the questions, not the outcome of this particular account comparison.