NoPartySubIDs (FIX tag 802)

NumInGroupFIX 4.4FIX 5.0 SP2group counter

NoPartySubIDs (tag 802) is a NumInGroup field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 44 message types, always optionally. Its datatype is NumInGroup, which makes it a repeating-group counter: its value is the number of entries that follow, not a quantity in its own right.

At a glance

Tag
802
Name
NoPartySubIDs
Datatype
NumInGroup (int)
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
44

What the specification says

Number of PartySubID (523)and PartySubIDType (803) entries

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

A real message using tag 802

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength181
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
453NoPartyIDs1 entry1repeating group
448PartyIDEXAMPLE
802NoPartySubIDs2 entries2repeating group
523PartySubIDEXAMPLE
523PartySubIDEXAMPLE
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
10CheckSum227
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 802 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 5.0 SP2Where in the message
AdjustedPositionReportBLOptionalinside Parties › PtysSubGrp
AllocationInstructionJOptionalOptionalinside Parties › PtysSubGrp
AllocationInstructionAckPOptionalOptionalinside Parties › PtysSubGrp
AllocationInstructionAlertBMOptionalinside Parties › PtysSubGrp
AllocationReportASOptionalOptionalinside Parties › PtysSubGrp
AllocationReportAckATOptionalOptionalinside Parties › PtysSubGrp
ApplicationMessageRequestBWOptionalinside Parties › PtysSubGrp
ApplicationMessageRequestAckBXOptionalinside Parties › PtysSubGrp
AssignmentReportAWOptionalOptionalinside Parties › PtysSubGrp
CollateralAssignmentAYOptionalOptionalinside Parties › PtysSubGrp
CollateralInquiryBBOptionalOptionalinside Parties › PtysSubGrp
CollateralInquiryAckBGOptionalOptionalinside Parties › PtysSubGrp
CollateralReportBAOptionalOptionalinside Parties › PtysSubGrp
CollateralRequestAXOptionalOptionalinside Parties › PtysSubGrp
CollateralResponseAZOptionalOptionalinside Parties › PtysSubGrp
ConfirmationAKOptionalOptionalinside Parties › PtysSubGrp
ContraryIntentionReportBOOptionalinside Parties › PtysSubGrp
CrossOrderCancelReplaceRequesttOptionalOptionalinside SideCrossOrdModGrp › Parties › PtysSubGrp
CrossOrderCancelRequestuOptionalOptionalinside SideCrossOrdCxlGrp › Parties › PtysSubGrp
ExecutionReport8OptionalOptionalinside Parties › PtysSubGrp
IOI6Optionalinside Parties › PtysSubGrp
ListCancelRequestKOptionalinside Parties › PtysSubGrp
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › Parties › PtysSubGrp
MarketDataRequestVOptionalinside Parties › PtysSubGrp
MarketDataRequestRejectYOptionalinside Parties › PtysSubGrp
MarketDataSnapshotFullRefreshWOptionalinside MDFullGrp › Parties › PtysSubGrp
MassQuoteiOptionalOptionalinside Parties › PtysSubGrp
MassQuoteAcknowledgementbOptionalOptionalinside Parties › PtysSubGrp
MultilegOrderCancelReplaceACOptionalOptionalinside Parties › PtysSubGrp
NewOrderCrosssOptionalOptionalinside SideCrossOrdModGrp › Parties › PtysSubGrp
NewOrderListEOptionalOptionalinside ListOrdGrp › Parties › PtysSubGrp
NewOrderMultilegABOptionalOptionalinside Parties › PtysSubGrp
NewOrderSingleDOptionalOptionalinside Parties › PtysSubGrp
OrderCancelReplaceRequestGOptionalOptionalinside Parties › PtysSubGrp
OrderCancelRequestFOptionalOptionalinside Parties › PtysSubGrp
OrderMassActionReportBZOptionalinside Parties › PtysSubGrp
OrderMassActionRequestCAOptionalinside Parties › PtysSubGrp
OrderMassCancelReportrOptionalinside Parties › PtysSubGrp
OrderMassCancelRequestqOptionalinside Parties › PtysSubGrp
OrderMassStatusRequestAFOptionalOptionalinside Parties › PtysSubGrp
OrderStatusRequestHOptionalOptionalinside Parties › PtysSubGrp
PositionMaintenanceReportAMOptionalOptionalinside Parties › PtysSubGrp
PositionMaintenanceRequestALOptionalOptionalinside Parties › PtysSubGrp
PositionReportAPOptionalOptionalinside Parties › PtysSubGrp
QuoteSOptionalOptionalinside Parties › PtysSubGrp
QuoteCancelZOptionalOptionalinside Parties › PtysSubGrp
QuoteRequestROptionalOptionalinside QuotReqGrp › Parties › PtysSubGrp
QuoteRequestRejectAGOptionalOptionalinside QuotReqRjctGrp › Parties › PtysSubGrp
QuoteResponseAJOptionalOptionalinside Parties › PtysSubGrp
QuoteStatusReportAIOptionalOptionalinside Parties › PtysSubGrp
QuoteStatusRequestaOptionalOptionalinside Parties › PtysSubGrp
RFQRequestAHOptionalinside Parties › PtysSubGrp
RegistrationInstructionsoOptionalOptionalinside Parties › PtysSubGrp
RegistrationInstructionsResponsepOptionalOptionalinside Parties › PtysSubGrp
RequestForPositionsANOptionalOptionalinside Parties › PtysSubGrp
RequestForPositionsAckAOOptionalOptionalinside Parties › PtysSubGrp
SettlementInstructionRequestAVOptionalOptionalinside Parties › PtysSubGrp
SettlementInstructionsTOptionalOptionalinside SettlInstGrp › Parties › PtysSubGrp
SettlementObligationReportBQOptionalinside SettlObligationInstructions › Parties › PtysSubGrp
StreamAssignmentReportCDOptionalinside StrmAsgnRptGrp › Parties › PtysSubGrp
StreamAssignmentRequestCCOptionalinside StrmAsgnReqGrp › Parties › PtysSubGrp
TradeCaptureReportAEOptionalOptionalinside TrdCapRptSideGrp › Parties › PtysSubGrp
TradeCaptureReportAckAROptionalinside TrdCapRptAckSideGrp › Parties › PtysSubGrp
TradeCaptureReportRequestADOptionalOptionalinside Parties › PtysSubGrp

Wire format

The number of entries in the repeating group that follows. The next field on the wire is the group's delimiter tag. @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 802 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);// NoPartySubIDs is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[802] is undefined.const entries = message.groups[802] ?? [];for (const entry of entries) {  // entry.fields is keyed by tag; entry.groups holds nested groups}

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