LiquidityNumSecurities (FIX tag 441)

intFIX 4.4FIX 4.2

LiquidityNumSecurities (tag 441) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type, always optionally.

At a glance

Tag
441
Name
LiquidityNumSecurities
Datatype
int
Dialects
FIX 4.4 and FIX 4.2
Messages
1

What the specification says

FIX 4.4

Number of Securities between LiquidityPctLow (402) and LiquidityPctHigh (403) in Currency.

FIX 4.2

Number of Securities between LiquidityPctLow and LiquidityPctHigh in Currency.

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

A real message using tag 441

BidRequest · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength135
35MsgTypekBid Request
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
391ClientBidIDEXAMPLE
374BidRequestTransTypeNNew
393TotNoRelatedSym1
394BidType1"Non Disclosed" Style (e.g. US/European)
398NoBidDescriptors2 entries2repeating group
399BidDescriptorType1Sector
441LiquidityNumSecurities1
399BidDescriptorType1Sector
441LiquidityNumSecurities1
418BidTradeTypeRRisk Trade
419BasisPxType2Closing Price at morning session
10CheckSum206
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 441 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
BidRequestkOptionalOptionalinside the BidDescReqGrp component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 441 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[441];field?.name;   // "LiquidityNumSecurities"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other int 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