NinjaTrader bridge: tick feed from an NT8 chart on port 7272
The NinjaTrader bridge streams tick-by-tick history and live trades from a running NinjaTrader 8 chart into Senzoukria over a loopback TCP socket. No broker credentials are entered in Senzoukria: the NT8 chart, its data feed and its Tick Replay setting do the work.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- Account → Broker Connections → + Add connection → NinjaTrader Bridge (kind: Bridge), then Chart data source → NinjaTrader
- Transport
- TCP on 127.0.0.1, port 7272 by default (the ATAS variant of the same indicator uses 7274)
- Platform
- Windows only — the option is greyed out with a "Windows only" tag on other systems
- Credentials
- None. The catalog entry reads "Streams data from a running NinjaTrader 8 chart via the local Orderflow bridge (no credentials)"
What it does
The bridge is a NinjaScript indicator, OrderflowBridge.cs, that you compile inside NinjaTrader 8 and add to a chart. It opens a listener on 127.0.0.1:7272 and, when Senzoukria connects, sends a one-shot header with the symbol and tick size, the whole historical tick batch of the chart, an end-of-history sentinel, then live ticks, an exchange-pushed daily volume line and a keep-alive ping every 5 seconds. The indicator binds on loopback only and never on 0.0.0.0.
On the Senzoukria side, every tick is written to the same footprint engine the native Rithmic adapter uses, so the footprint, the DOM ladder, drawings, indicators and the sim trading panel behave exactly as on a direct connection. After the transition to live, the chart pulls a bar snapshot to recover any update that was evicted during the replay burst.
The bridge is a Bridge-kind entry in the broker catalog: it appears in the Add connection wizard as "NinjaTrader Bridge" with the note "Local loopback connection (port 7272)". The chart reads it once "NinjaTrader" is chosen in the Chart data source selector, whose hint reads "Local bridge — NT8 chart must be running".
Setting up the NT8 chart
| Setting | Value | Why it matters |
|---|---|---|
| Indicator file | Documents\NinjaTrader 8\bin\Custom\Indicators\OrderflowBridge.cs, compiled with F5 (0 errors) | The bridge is an indicator; it must compile before it can be added to a chart |
| Bars Period type / value | Tick / 100 | A 1-Tick chart over 24 h of MNQ creates 5M+ NT bars and hits internal limits; 100 Tick keeps per-tick callbacks with ~30k bars |
| Tick Replay | ON (Properties → Data Series) | Without it NT hands over aggregated bars; the app raises the persistent "NT misconfigured" banner (reason no-seq) |
| Port (indicator property) | 7272, range 1024–65535 | Must match the port Senzoukria connects to |
| TickSize (fallback) | 0.25 | Ignored in normal use: the bridge reads the real tick size from the instrument |
| Output window | "OrderflowBridge: listening on 127.0.0.1:7272" | The line that confirms the listener is up |
Status banner and warnings
- "Bridge: connecting to NinjaTrader on 127.0.0.1:7272…" while the socket opens; "Replaying history: n / total (pct%)" during the historical batch; the LIVE indicator of the status bar once live ticks flow.
- "Bridge dropped. Reconnecting in Ns…" when the socket closes — the app reconnects on its own, and the backfill merges by bucket without wiping the chart.
- A "⚠ drift N" badge next to the timeframe pills when NT announced more historical ticks than were received: tick-based bars (100T) may not align bar-for-bar with NT for that session. Reconnect to retry.
- A persistent orange "NT misconfigured" banner when the wire carries no sequence counter: OrderflowBridge.cs is older than v2 or Tick Replay is OFF. It stays visible even in the live state, because a silently wrong footprint would be worse.
- A diagnostic button copies the visible bars as CSV, in a format comparable to NinjaTrader's footprint "Save as" export, to diff OHLC, volume and per-cell bid × ask row by row.
Limits and pitfalls
Both programs must stay open: closing NinjaTrader closes the bridge. The bridge carries market data and depth for the instrument on the NT chart only; switching the NT chart's instrument resets the per-timeframe bars in Senzoukria for the new symbol. Depth arrives as aggregated L2, so the DOM shows no MBO iceberg badge (that badge is Rithmic-only).
The data itself is the data NinjaTrader receives: its licence, its session and its vendor apply. Nothing in the bridge creates history that the NT chart does not have — the chart's loaded range (for example 24 hours) is what gets replayed.
Related pages
This page in other languages
Frequently asked questions
- Does the NinjaTrader bridge need my broker password?
- No. NinjaTrader keeps its own session with your broker or data vendor; the bridge only forwards ticks over loopback. Senzoukria stores nothing for this connection.
- Why must the chart be a 100 Tick chart and not 1 Tick?
- A 1-Tick chart over a day of MNQ creates millions of NinjaTrader bars and hits internal limits, which decorrelates 1-minute candles from NT's own chart. With 100 Tick and Tick Replay ON, OnMarketData still fires per tick, so the granularity is kept without saturating NT.
- The chart shows bars but no order flow. What is wrong?
- The platform is sending bars without ticks: check that the chart is on ticks and that Tick Replay is ON in its Data Series settings. Both settings live in NinjaTrader, not in Senzoukria.