NoLinesOfText (FIX tag 33)

NumInGroupFIX 4.4FIX 4.2group counter

NoLinesOfText (tag 33) is a NumInGroup field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types and is required in 2 of them. 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. FIX 4.2 calls this field LinesOfText; the tag number is unchanged, so the two are the same field on the wire.

Also known as LinesOfText
FIX 4.2 calls tag 33 LinesOfText. It is the same field on the wire — only the name changed — so a message encoded by either side interoperates.

At a glance

Tag
33
Name
NoLinesOfText
Datatype
NumInGroup (int)
Dialects
FIX 4.4 and FIX 4.2
Messages
2

What the specification says

Identifies number of lines of text body

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

A real message using tag 33

News · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength188
35MsgTypeBNews
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
148HeadlineEXAMPLE
33NoLinesOfText2 entries2repeating group
58TextExample message generated from the FIX dictionary.
58TextExample message generated from the FIX dictionary.
10CheckSum203
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 33 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
EmailCRequiredRequiredinside the LinesOfTextGrp component
NewsBRequiredRequiredinside the LinesOfTextGrp component

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 33 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);// NoLinesOfText is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[33] is undefined.const entries = message.groups[33] ?? [];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