Skip to main content

Historical Data For Backtesting

Customers often ask why a DAX/GER40 chart only shows one to three months of data, or where to get more data for BananaEA backtests. The short answer is:

info

Use the broker-server history for the exact MT4 symbol and server you intend to trade whenever possible. Generic DAX, Germany 40, or third-party data can be useful for research, but it will not be identical to your broker's CFD chart.

For Pepperstone MT4 users, the most relevant data source is the Pepperstone MT4 trade server history for the exact symbol shown in Market Watch, such as GER40, GER40.r, GER40.cash, or another account-specific name.

Why The Chart Only Shows A Short Period​

MT4 does not always load the full available history immediately. A new terminal may only show recent bars until you request more chart history.

Common reasons:

  • The terminal has not downloaded older bars yet.
  • Max bars in history or Max bars in chart is set too low.
  • You are logged in to a different broker server, account type, or symbol variant.
  • The broker server does not provide more history for that symbol/timeframe.
  • Imported or downloaded history does not match the broker symbol being tested.

Best Source: Broker MT4 Server History​

Use this process first, especially for DAX/GER40 backtests:

  1. Log in to the correct MT4 account and broker server.
  2. Open Market Watch and confirm the exact symbol name.
  3. Go to Tools > Options > Charts.
  4. Increase Max bars in history and Max bars in chart.
  5. Restart MT4.
  6. Open the DAX/GER40 chart, starting with M1.
  7. Press Home repeatedly or scroll left until MT4 stops loading older bars.
  8. Repeat for the timeframes you need, or rebuild higher timeframes from clean M1 data.

For BananaEA testing, M1 data is the most useful base because higher timeframes can be built from it. If you only test H1, still check that the lower-timeframe history is available and clean.

warning

If the broker server stops loading after one to three months, MT4 cannot invent broker-specific history. Contact the broker and ask whether more MT4 bar data is available for the exact symbol and server.

Useful support request wording:

Please provide historical MT4 bar data for [exact symbol] on [exact server],
preferably M1 OHLCV from [start date] to [end date].

Record whether the data came from a live or demo server, the account type, the symbol name, and the broker server timezone.

Be Careful With History Center Download​

MT4 has Tools > History Center, and it supports downloading, importing, and exporting historical data. However, MetaTrader's own documentation warns that data downloaded from the historical data server can differ from the data stored on the broker's trade server.

For BananaEA, treat History Center downloads as a backup option, not the main source for broker-specific validation.

SourceUseful ForLimitation
Broker-server MT4 historyClosest match to the chart you tradeLimited to what the broker server provides
MT4 History Center downloadFilling gaps or basic checksMay not match broker-specific CFD history
Dukascopy or TickstoryLonger research and stress testingNot Pepperstone or your broker's feed
Official DAX/index dataReference price directionNot broker CFD pricing, spread, or MT4 timestamps
Public charting sitesRough visual comparisonUsually not suitable for EA validation

Third-Party Data Sources​

Third-party data can help when you need a longer research sample, but it must be labelled clearly.

Dukascopy Or Tickstory​

Dukascopy lists a Germany 40 Index CFD instrument as DEU.IDX/EUR, and Tickstory is commonly used to export Dukascopy data into MT4-friendly formats.

This can be useful for broad stress tests, but it is not Pepperstone data and not guaranteed to match any MT4 broker. Before using it, check:

  • symbol name
  • digits and point size
  • spread assumptions
  • contract size
  • trading hours
  • broker server timezone
  • session gaps and holidays

Official DAX Or Public Website Data​

Official exchange/index data, Yahoo Finance, Investing.com, and TradingView can be useful for broad comparison. They are not a substitute for MT4 broker CFD history because they usually do not reproduce broker spread, bid/ask behavior, CFD session handling, tick volume, or server timestamps.

Sharing MT4 History With Another User​

Technically, MT4 history can be shared. CSV is usually easier to audit than copying MT4 .hst files.

danger

Check the broker's current data and platform terms before redistributing broker price data. Do not publicly package or sell broker historical data unless the broker or data owner permits it.

On the source MT4 terminal:

  1. Open Tools > History Center or press F2.
  2. Select the exact symbol and timeframe.
  3. Click Export.
  4. Save the file as CSV.
  5. Label the file with broker, server, symbol, timeframe, date range, and timezone.

Example filename:

Pepperstone-Live01_GER40_M1_2024-09-01_to_2026-05-01_MT4-server-time.csv

A typical MT4 bar file contains:

YYYY.MM.DD,HH:MM,Open,High,Low,Close,Volume

In MT4, chart volume is normally tick volume, not official exchange volume.

On the receiving MT4 terminal:

  1. Back up existing history first.
  2. Open Tools > History Center.
  3. Select the matching symbol and timeframe.
  4. Click Import.
  5. Confirm separator, date/time format, and volume import.
  6. Restart MT4.
  7. Verify the first and last dates on the chart.

The receiving user should import into the same symbol name where possible. A file exported for GER40 may not behave correctly if imported against GER40.r, GER40.cash, or another broker-specific symbol without careful adjustment.

Advanced Method: .hst Files​

MT4 stores separate .hst files by symbol and timeframe inside the terminal data folder.

Typical location:

File > Open Data Folder > history > [server name]

Example files:

GER401.hst
GER405.hst
GER4015.hst
GER4060.hst
GER40240.hst
GER401440.hst

The number is the timeframe in minutes:

File suffixTimeframe
1M1
5M5
15M15
30M30
60H1
240H4
1440D1

Only copy .hst files while MT4 is fully closed, and always back up the recipient's existing history first. CSV is usually safer because it is easier to inspect, transform, and re-import.

BananaEA Backtesting Rules​

When using imported or shared data with BananaEA:

  • Do not claim a third-party dataset is broker-specific unless it came from that broker server.
  • Keep broker, server, symbol, timeframe, date range, and timezone in your notes.
  • Use realistic spread and commission assumptions in Strategy Tester.
  • Check for missing bars, incorrect prices, session gaps, and sudden jumps.
  • Separate chart-history validation from live execution validation.
  • Forward test on demo before using settings live.

M1 OHLCV history can improve chart consistency, but it does not fully reproduce live trading. It normally does not include a true historical ask stream, variable spread, slippage, broker rejections, liquidity changes, or news execution behavior.

If a setup depends heavily on spread, scalping, precise intrabar movement, stop placement, session gaps, or news spikes, historical bar data alone is not enough to prove the setup.