GBP/JPY historical data for pound yen backtests
Audited OHLCV files for British Pound / Japanese Yen yen-cross backtesting, Python research, and local data workflows. The current release lists 3,864,370 total source-observed rows across 7 Parquet files, including 2,996,692 M1 rows.
GBP/JPY is a complete-bundle pair in the current uploaded release, not a standalone product claim. Use the audited rows, dates, and gap checks before treating it as suitable for a pound-yen strategy.
Audit Snapshot
GBP/JPY query fit
Pound yen historical data for backtest checks
If you are searching for GBP/JPY historical data, start by checking the audited row counts and coverage dates before you wire the file into a yen-cross strategy. The current release exposes 3,864,370 source-observed rows across 7 Parquet files, including 2,996,692 M1 rows.
What this page proves
This page is not a blanket completeness claim. It exposes the audited row count, coverage range, and validation checks we can verify from the current release artifacts.
Parquet-first
Typed columns load directly in pandas, DuckDB, R, and modern data tooling.
Coverage-aware
Known gaps are handled through pair-specific reports instead of hidden continuity claims.
Research-ready
M1 bars are packaged with derived timeframes for repeatable local backtesting workflows.
Release note
GBP/JPY is included in the uploaded complete bundle. Coverage and gap counts vary by symbol, so buyers should use the pair-specific audit snapshot before assuming suitability for a backtest.
Need this symbol for a specific backtest?
Ask for manual order help if you need confirmation on GBP/JPY delivery fit, invoices, team use, custom validation, or whether this symbol belongs in a larger bundle for your strategy.
This is an inquiry path, not a gap-free promise. Coverage ranges and quality checks remain visible before any paid delivery.