TL;DR
Tick data records every single trade with exact timestamp, price, and size; bar data (OHLCV) groups all trades in a fixed time period into five summary values — tick data gives full precision for high-frequency analysis, bar data is sufficient for most systematic strategies and exponentially easier to work with.
What Is Tick Data vs Bar Data?
Tick data is the most granular level of market data — a record of every individual transaction that occurs, including the exact time (to the millisecond or microsecond), the price at which the trade occurred, and the number of contracts or shares exchanged. In an active market, this can generate millions of data points per day per instrument. On liquid NSE index-options strikes near the money during expiry-week sessions, tick counts can run into the hundreds of thousands per contract per day.
Bar data (also called OHLCV data) aggregates all ticks within a fixed time interval — 1 minute, 5 minutes, 1 hour, 1 day — into five summary values: the first tick’s price (Open), the highest tick price (High), the lowest tick price (Low), the last tick’s price (Close), and the total volume of all ticks (Volume). The result is a manageable dataset that discards the intrabar path to focus on the period’s net result.
The choice between tick and bar data depends on the strategy’s time horizon and requirements. High-frequency trading (HFT) strategies that measure edge in milliseconds require tick data — at that scale, every individual transaction matters and OHLCV bars aggregate too much. Systematic strategies that operate on 1-minute, 5-minute, or daily bars have no use for tick-level granularity; bar data is both sufficient and computationally practical. The vast majority of TradingView-based systematic trading — including most NIFTY and Bank Nifty intraday index-options strategies — operates on bar data.
Key Formula / Numbers
Data volume comparison:
| Market | Tick Data Volume | Daily Bar Data |
|---|---|---|
| S&P 500 futures (liquid) | ~5-50 million ticks/day | 1 daily bar |
| EUR/USD forex | ~50-200 million ticks/day | 1 daily bar |
| Bitcoin (major exchange) | ~500K-2M ticks/day | 1 daily bar |
| NIFTY 50 index (NSE cash) | Millions of ticks/day across constituents | 1 daily bar |
| NIFTY near-the-money weekly option (expiry day) | Can exceed 100K ticks/day at peak strikes | 1 daily bar |
Bar types derived from tick data:
| Bar Type | Aggregation Method |
|---|---|
| Time bars (OHLCV) | Fixed time period (most common) |
| Tick bars | Fixed number of trades |
| Volume bars | Fixed volume of contracts/shares |
| Dollar bars | Fixed dollar value traded |
| Renko bars | Fixed price movement, ignores time |
Worked Example — Same NIFTY Move, Two Views
Say NIFTY trades in a 20-point range over one minute, printing hundreds of individual ticks as it moves up, back down, and up again before settling.
- Tick view: every one of those individual trades is a separate record — the exact sequence of up-ticks and down-ticks, each with its own timestamp and traded size, showing the full intrabar path.
- 1-minute bar view: that entire minute collapses to five numbers — Open (the first tick’s price), High (the highest tick reached), Low (the lowest tick reached), Close (the last tick’s price), and Volume (the sum of all traded size in the window).
A strategy that generates a signal only at bar close (e.g. “close above the 20-period moving average on the 5-minute chart”) gets everything it needs from the bar view — the specific up/down sequence inside that 5 minutes is irrelevant to a signal that only checks the close. A market-making or ultra-short scalping strategy trying to capture the bid-ask spread on individual prints, by contrast, needs the tick view because its edge lives entirely inside that intrabar path the bar data discards.
How Quantzee Uses This
Quantzee indicators run on TradingView’s bar data (OHLCV), which is the standard for the platform’s indicator ecosystem. The non-repainting architecture is specifically a bar-data property: signals lock at bar close, meaning the complete OHLCV data for that bar is finalized before the signal is recorded. Tick-level intrabar movement does not affect Quantzee signals — the bar close price is the definitive input, which is both the non-repainting guarantee and the practical reason why bar-data-based strategies are more reproducible than tick-based ones.
This matters directly for NIFTY/Bank Nifty intraday traders: because the AI Adaptive Quant Toolkit’s Supertrend matrix and Smart Trail logic evaluate at bar close on whatever timeframe you’ve selected, the signal you see mid-bar can still finish differently by close — this is normal, expected non-repainting behavior, not a data-quality issue, and it’s the same reason a strategy validated on bar-close logic in backtesting should also be traded on bar-close confirmation live.
Common Mistakes
- Assuming higher granularity always produces better backtests: Tick-level backtesting introduces additional noise and complexity without improving predictive power for strategies that genuinely operate on bar-level logic. If your strategy uses bar-close signals, bar data is sufficient — adding tick-level resolution introduces spurious precision.
- Ignoring the bid-ask spread in tick data analysis: Raw tick data often includes both buy-initiated and sell-initiated trades at slightly different prices. Analyzing tick data without accounting for the bid-ask spread can create phantom patterns from the normal bid-ask oscillation — this is closely related to how liquidity affects fill quality on wider-spread instruments like far OTM options.
- Using time bars for volume-sensitive strategies: Fixed time bars don’t account for varying market activity — a 1-minute bar during the NSE’s opening 15 minutes may contain far more transactions than the same 1-minute bar in the mid-afternoon lull. Volume bars or dollar bars normalize for this, giving each bar a consistent “amount of market” regardless of the time period.
- Misreading a circuit-halt bar as a signal: A flat or gapped OHLCV bar caused by an NSE price-band halt looks structurally similar to a genuine low-volatility consolidation bar. Strategies that don’t separately flag halted periods can generate false signals off a bar that wasn’t actually trading.