Set up Timeframe and Time Range in backtest

Jan 13, 2026

5 min read

Master Timeframe vs. Time Range in backtesting to stop losing money on overfitted bots. Learn why flexible historical data is key to profitable crypto strategies on Buddytrading.

Whether you are building a simple MACD cross strategy or a complex algorithm, the difference between a profitable bot and a broken bank account often comes down to two settings: Timeframe and Time Range.

In this week's journal, we are breaking down these two critical backtesting toggles. They might sound similar, but they control completely different parts of your bot's logic.

Understanding Timeframe

The Timeframe dictates how often your bot checks the market prices to make a decision.

In technical terms on Buddytrading, the Timeframe is the specific interval at which the On Enter logic in your code executes.

Fast Timeframes (1 Minute / 15 Minutes): Your bot checks the market constantly. This is often used for strategies that try to grab small profits from quick price movements. However, checking this often means your bot might react to random "noise" or tiny price jumps.
Slow Timeframes (4 Hours / 1 Day): Your bot waits longer between checks. This helps ignore the noise and focus on bigger, stronger trends. This is typically used for strategies that want to ride a long-term market movement.

Understanding Time Range

While Timeframe is about frequency, Time Range is about duration. It defines how much historical data you want to test your strategy against.

When you run a backtest, you are asking the system to simulate your bot's performance over a specific period in the past.

Short Range (1 Week): This is useful for quickly checking if your code works technically or seeing how the bot handles a very specific recent event.
Long Range (1 Month / 3 Months): This is the standard for reliability. Testing over a longer period ensures your bot faces different market conditions, such as price crashes, rallies, or stagnant markets.