Nasdaq Stock Market, Nasdaq BX and Nasdaq PSX. Order-by-order, full depth.
Recorded replay
Replay · not live--:--:--Nasdaq TotalView-ITCH 5.0, public Nasdaq sample day, 2019-12-30, 10:00 ET, 5 minutes at original speed, looping. Every packet is decoded by our MD handler; the books below are its output.
-
packets / s (whole feed)
-
book updates / s (whole feed)
book updates per second over the recording; the orange line is now
Venue
Nasdaq Stock Market, Nasdaq BX and Nasdaq PSX
Asset class
US Equities
Wire format
Binary messages in MoldUDP64 packets over multicast UDP; order by order, every add, execute, cancel, delete and replace with an order reference number.
Messages
System Event, Stock Directory, Trading Action, Reg SHO, Market Participant Position, MWCB, IPO Quoting Period, LULD Auction Collar, Add Order / with MPID, Order Executed / with Price, Order Cancel, Order Delete, Order Replace, Trade, Cross Trade, Broken Trade, NOII, RPII
Book
Order-by-order, full depth
Sequencing
MoldUDP64 sequence per channel (count 0 = heartbeat, 0xFFFF = end of session); gaps reported, duplicates skipped, resets detected. Recovery (MoldUDP64 retransmission or GLIMPSE snapshot) is set up per client deployment.
Validation
Validated in our production handler framework (MD) on Nasdaq's public sample days, against reference decoders we wrote independently from the ITCH 5.0 specification. Nasdaq (2019-12-30, 268.7 million messages, 2026-11-17): all 199,354 AAPL top-of-book states matched in order; all 8,906 symbols processed with zero errors, no crossed books, every book empty at the close; about 2.6 million messages per second on one core. BX and PSX (same day, 2026-11-20), every symbol checked: BX 7,380 symbols and 22.4 million top-of-book states, PSX 6,828 symbols and 33.4 million states, all identical to the reference, zero errors. Exchange-direct input: our production handler does not yet take live UDP multicast, so this handler runs on captures in our test tools today; live multicast input and gap recovery are in development.
Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.
This handler is not running in our public stack. It is built for clients with their own exchange connectivity and licences; live multicast input is in development.