NetChgPrevDay (FIX tag 451)

PriceOffsetFIX 4.4FIX 5.0 SP2

NetChgPrevDay (tag 451) is a PriceOffset field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag: 451
Name: NetChgPrevDay
Datatype: PriceOffset (float)
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 2

What the specification says

FIX 4.4

Net change from previous day’s closing price vs. last traded price.

FIX 5.0 SP2

Net change from previous day's closing price vs. last traded price.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 451

MarketDataSnapshotFullRefresh · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	87
35	MsgType	W	Market Data-Snapshot/Full Refresh
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
451	NetChgPrevDay	0.00010
268	NoMDEntries1 entry	1	repeating group
269	MDEntryType	0	Bid
10	CheckSum	032

Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 451 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	FIX 4.4	FIX 5.0 SP2	Where in the message
MarketDataIncrementalRefresh	X	Optional	Optional	inside the MDIncGrp component
MarketDataSnapshotFullRefresh	W	Optional	Optional	directly on the message body

Wire format

A signed decimal price delta. Negative values are legal and meaningful. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 451 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[451];field?.name;   // "NetChgPrevDay"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other PriceOffset fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44

Try the decoder Source on GitHub