· DELTA
Why delta differs between two platforms on the same contract
Delta can differ between two platforms on the same ES session. Liquivue and NinjaTrader on one bridge feed trace a 1,920 contract gap to its causes.
SHORT ANSWER
Delta differs between two platforms when they start cumulative delta at different times, classify trades by different rules, or filter and group trades differently. Different data feeds add another gap. Liquivue on the NinjaTrader bridge reads the same trades as NinjaTrader 8, so any gap between their delta numbers comes from settings, not from the data.
Delta differs between two platforms on the same contract because each platform sets its own start time and classification rule before it subtracts. Delta is the volume bought by aggressive buyers minus the volume sold by aggressive sellers. Cumulative delta adds that number up from a start time. This note takes one invented ES morning, reads cumulative delta in Liquivue and in NinjaTrader at the same moment, and traces the gap step by step. The note on what a delta number counts covers how a trade gets its side.
Why the bridge makes a clean test
Two platforms on two data feeds can receive different trades. One feed may join fills that the other splits, and one may drop trades the other keeps. That makes any gap hard to explain.
The NinjaTrader bridge removes that cause. NinjaTrader 8 connects to the data provider, and the bridge passes the trades it receives to Liquivue on the same computer. Both platforms count the same trades. Any gap between them comes from settings. The note on using NinjaTrader as a data bridge covers the setup.
The two readings at 10:30
All numbers below are invented. The contract is ESZ6, the December 2026 E-mini S&P 500 future.
At 10:30 New York time, the Liquivue CVD reads plus 1,240. The NinjaTrader cumulative delta reads plus 3,160. The gap is 1,920 contracts.
Step 1, align the start time
The first question is where each count starts. ES trades from 18:00 New York time the evening before. Some charts start cumulative delta there. Others start at the 9:30 open of regular trading hours.
In this example the Liquivue CVD starts at 18:00 the previous evening. The NinjaTrader chart starts at 9:30. The overnight session from 18:00 to 9:30 had a delta of minus 2,100.
| Reading | Liquivue | NinjaTrader |
|---|---|---|
| Delta from 18:00 to 9:30 | minus 2,100 | not counted |
| Delta from 9:30 to 10:30 | plus 3,340 | plus 3,160 |
| Reading at 10:30 | plus 1,240 | plus 3,160 |
With both counts starting at 9:30, the gap falls from 1,920 to 180 contracts. Liquivue backfills 1 to 96 hours of trades, depending on the provider. An 18:00 start at 10:30 the next morning needs 16.5 hours of trades.
Step 2, check how history was classified
The second question is how each platform gave a side to trades it loaded from history. In this example the NinjaTrader chart opened at 9:45, so it built the first 15 minutes from historical data.
NinjaTrader Order Flow+ volumetric bars need historical bid and ask tick data to classify history by BidAsk. BidAsk compares each trade price with the bid and the ask. When history holds last prices only, NinjaTrader offers UpDownTick instead. A tick rule like UpDownTick compares each trade price with the previous trade. A higher price counts as a buy, a lower price counts as a sell, and an unchanged price keeps the previous side.
The two rules split when the quotes move between trades. Here are five ES trades. The bid and ask start at 5,051.00 and 5,051.25, and both rise one tick before trade 3.
| Trade | Bid and ask | Price | Size | BidAsk side | UpDownTick side |
|---|---|---|---|---|---|
| 1 | 5,051.00 by 5,051.25 | 5,051.25 | 10 | Buy | Buy |
| 2 | 5,051.00 by 5,051.25 | 5,051.00 | 20 | Sell | Sell |
| 3 | 5,051.25 by 5,051.50 | 5,051.25 | 30 | Sell | Buy |
| 4 | 5,051.25 by 5,051.50 | 5,051.25 | 15 | Sell | Buy |
| 5 | 5,051.25 by 5,051.50 | 5,051.50 | 25 | Buy | Buy |
Trade 3 hit the new bid, so BidAsk calls it a sell. Its price was one tick above trade 2, so UpDownTick calls it a buy. Trade 4 printed at the same price and keeps that buy. BidAsk gives a delta of minus 30 for the five trades. UpDownTick gives plus 60.
In this example, the 9:30 to 9:45 window classified by BidAsk gives plus 410. The same trades classified by UpDownTick give plus 230. That difference of 180 matches the remaining gap. After 9:45 both platforms classify live trades the same way in this example, and their numbers move together.
Other causes when a gap remains
If a gap remains after these two steps, check the trade size filter next. A filter that drops trades under 10 contracts changes delta, and the note on delta on large trades only shows by how much. Fill grouping matters only through that filter. Joining eight 5 lot fills into one 40 lot trade leaves delta unchanged, but the 40 lot passes a 10 contract filter and the 5 lots do not. If the two platforms do not share one feed, the data itself is the last thing to check.
Delta on other platforms
ATAS documents limits by connector. Its dxFeed connector lists the Delta and Cumulative Trades chart variants as unsupported, so the same plan can offer different delta views on different data. NinjaTrader lists cumulative delta in Order Flow+. Liquivue draws CVD with volume and delta profiles beside its heatmap, and its docked HTF chart has a delta footprint. In Liquivue the CVD line, the delta footprint rows and the trade bubbles are on one screen, so you can check a delta reading against the trades that built it.
A check you can run
Open the same contract in two platforms and write down each cumulative delta at one exact time. Then write down each start time. Subtract the delta from the earlier start to the later one and see how much of the gap is left. If a gap remains, compare one bar from history with one live bar.
Questions
Why is my cumulative delta different on two platforms?
The two platforms usually start the count at different times, classify some trades differently, or filter and group trades differently. If they also use different data feeds, the trades themselves can differ.
What is the difference between BidAsk and UpDownTick delta in NinjaTrader?
BidAsk classifies each trade by comparing its price with the bid and the ask, so it needs historical bid and ask tick data for past bars. UpDownTick classifies each trade by whether price ticked up or down from the last trade, and NinjaTrader offers it when history holds last prices only.
Does Liquivue use the same data as NinjaTrader on the bridge?
Yes. The NinjaTrader bridge passes the trades NinjaTrader 8 receives to Liquivue on the same computer. Any gap between Liquivue CVD and NinjaTrader cumulative delta on that route comes from settings such as the start time.
Which delta number is correct?
Both can be correct for their own settings. Pick one start time and one classification rule, write them down, and compare only numbers built the same way.
Educational content about market data and charting software. It is not trading or investment advice. Trading involves risk.