Quantower bridge: local tick feed from a Quantower chart on port 7273
The Quantower bridge is the second local bridge of Senzoukria. A plug-in inside Quantower streams the chart's historical and live ticks over 127.0.0.1:7273, and Senzoukria renders them with the full footprint feature set — no broker credentials, no vault.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- Account → Broker Connections → + Add connection → Quantower Bridge (kind: Bridge); then Chart data source → Quantower
- Transport
- TCP on 127.0.0.1, port 7273 (the NinjaTrader bridge uses 7272)
- Platform
- Windows only — the option is not selectable elsewhere and shows the "Windows only" tag
- Catalog note
- "Streams data from a running Quantower chart via the local Orderflow bridge (no credentials)" — "Local loopback connection (port 7273)"
What it does
The Quantower path is a mirror of the NinjaTrader bridge: identical logic, a different port and its own "quantower-*" state events. The plug-in on the Quantower side sends a header with the symbol and tick size, the full historical batch, an end-of-history sentinel, then live ticks. Senzoukria writes every tick into the same footprint engine as the native Rithmic adapter, so the drawing toolbar, indicators, sim trading panel, advanced settings modal, status bar, magnet toggle and timezone cycle are all available.
Depth is carried too: the DOM sidebar listens to the quantower-depth-update event and seeds itself with a one-shot snapshot for the current symbol. The depth payload has the same shape for the three connectors (bridge, Quantower, Rithmic), so the ladder is source-agnostic. Only Rithmic adds MBO iceberg detection; on Quantower the ladder shows aggregated L2 and hides the MBO badge.
The chart connects on mount: opening a footprint with Quantower as data source calls quantower_connect on host 127.0.0.1 and port 7273, and leaves the connection with quantower_disconnect when you switch source.
States shown on the chart
| State | What you see | What it means |
|---|---|---|
| connecting | "Bridge: connecting to Quantower on 127.0.0.1:7273…" | The socket is being opened; Quantower and its chart must already be running |
| receivingHistory | "Replaying history: received / total (pct%)" | The historical tick batch is being replayed into the engine |
| live | LIVE indicator in the status bar, banner hidden | Live ticks are flowing; a bar snapshot is pulled once to recover evicted updates |
| reconnecting | "Bridge dropped. Reconnecting in Ns…" | The socket closed; the app retries by itself and keeps the bars already drawn |
| drift | "⚠ drift N" badge next to the timeframe pills | Announced and received historical tick counts differ; 100T bars may not align with the platform |
| misconfigured | Persistent orange "QT misconfigured" banner | Reason no-seq: the plug-in is older than v2 or tick replay is OFF on the chart |
| dailyVolume | Session volume in the status bar | Exchange-pushed daily volume, shown next to the bar-summed counter |
How to use it
- Install the bridge add-on in Quantower's own plug-in folder and restart the platform; it must appear in the platform's indicator or plug-in list under its own name.
- Open a tick chart of the instrument you want and turn on tick-by-tick replay in that chart's data settings, otherwise the platform hands over aggregated bars and the order flow is lost before it reaches Senzoukria.
- In Senzoukria, add a Quantower Bridge connection, then pick "Quantower" in the Chart data source selector (hint: "Local bridge — Quantower must be running"). Bars appear, the last one moves, and the connection badge stays on.
- The "Guide me step by step" panel switches to its Bridge lane for a bridge backend, with three steps (Install the bridge add-on, Open a chart the bridge can read, Check the link on this side); the last one is confirmed by the history capability of the live connection snapshot.
Limits and pitfalls
Closing Quantower closes the bridge, and the bridge only carries the instrument of the chart it is attached to. The data licence, session and history depth are those of the Quantower feed. The bridge is Windows-only because Quantower is. Trading through the bridge is not part of this connection: the ticket and account panels follow the broker connection, not the tick stream.
Related pages
This page in other languages
Frequently asked questions
- Can I run the NinjaTrader and Quantower bridges at the same time?
- They listen on different ports (7272 and 7273), but the chart reads one data source at a time, chosen in the Chart data source selector.
- Why does the misconfiguration banner mention a sequence counter?
- Since v2 of the bridge, every tick carries a monotonic sequence number. When it is missing, the app cannot verify tick alignment, so it flags the plug-in as outdated or the chart as not replaying ticks, and keeps the banner even in the live state.