Define what “Ctrader Charts information” means
When people say they want to verify “information about cTrader Charts,” they usually mean one or more of these: (1) the price series shown on the chart, (2) how an overlay or calculation (for example, an indicator line) is computed, and (3) how chart results relate to what happens in an account (execution, spreads, commissions, and timing). Start by defining which of these you are trying to verify, because different checks apply to different kinds of information.
Use a source hierarchy to verify chart claims
A practical verification hierarchy is:
- Platform documentation for chart behavior and configuration terms (what inputs exist, what “timeframe” means, and what the chart actually displays).
- Your own setup and logs: the chart’s symbol, timeframe, timezone settings, and any data source settings available in the platform.
- Independent reproduction: confirm the same historical period using the same assumptions elsewhere when possible, or by re-deriving the computation from exported values.
- Account-level records (when relevant): executions, commissions, and journal/trade history to see how chart impressions map to realized outcomes.
If a claim is about something stable (for example, “this chart displays OHLC candles for the selected timeframe”), documentation and controlled tests are usually enough. If a claim is about something variable (for example, “this strategy will perform under market conditions X”), verification becomes an uncertainty assessment rather than a guaranteed check.
Verification steps you can reproduce
1) Lock the chart configuration
Write down the exact chart inputs you used: instrument/symbol, timeframe, timezone, and the visible date range. Make sure any settings that affect the displayed series are consistent between comparisons.
2) Check timestamps and session boundaries
A common failure mode is misaligned candles caused by timezone differences or session boundaries. Verify that the first and last candles you compare cover the same real-world time window, using the chart’s displayed timestamps and your local interpretation.
3) Re-derive displayed calculations from stated inputs
If the chart shows a calculated element (for example, an indicator value), verify it by identifying the computation inputs (lookback length, price type, and whether smoothing is applied). Then reproduce the calculation using the same historical data points and the same math.
Assumptions must be explicit: specify the exact price series used (bid/ask vs mid vs last, where applicable), the exact window length, and whether rounding is involved.
4) Compare chart series against exported or logged data
If the platform allows exporting data or provides a way to inspect the underlying series, export the relevant range and compare it to what the chart shows. If you cannot export, compare chart readings at known points (for example, candle open/high/low/close) by manually recording values and checking for internal consistency.
Limitations and failure modes to expect
Even with careful verification, some limitations can prevent certainty:
- Data feed differences: the displayed historical series can differ across environments, especially when “price type” or data source changes.
- Backtest vs chart mismatch: chart appearance does not automatically equal execution outcomes, because fills depend on spread, commission, slippage, and order timing.
- Missing or adjusted history: historical datasets can have gaps, revisions, or changes in corporate actions; relationships observed historically do not guarantee future behavior.
- Calculation assumptions: indicator or transformation results can change if inputs like price type, smoothing method, or timeframe aggregation differ.
In short, verification should tell you whether the information you observe is internally consistent with documented mechanics and your locked settings—not whether it predicts future results.
Turn verification into the next question you can answer
After you verify the mechanics (how the chart computes and displays values), narrow your question to something testable: for instance, whether a specific overlay corresponds to a specific formula under your chosen inputs. If a claim cannot be expressed as a reproducible check with defined assumptions, treat it as uncertain rather than as verified information.