NoTrdRegTimestamps (FIX tag 768)

NumInGroupFIX 4.4FIX 5.0 SP2group counter

NoTrdRegTimestamps (tag 768) is a NumInGroup field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 8 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: 768
Name: NoTrdRegTimestamps
Datatype: NumInGroup (int)
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 8

What the specification says

FIX 4.4

Number of TrdRegTimestamp (769) entries

FIX 5.0 SP2

Number of timestamp entries.

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

A real message using tag 768

TradeCaptureReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	223
35	MsgType	AE	Trade Capture Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
571	TradeReportID	EXAMPLE
570	PreviouslyReported	N	not reported to counterparty
32	LastQty	1000000
31	LastPx	1.09210
75	TradeDate	20240101
60	TransactTime	20240101-12:00:00.000
768	NoTrdRegTimestamps2 entries	2	repeating group
769	TrdRegTimestamp	20240101-12:00:00.000
769	TrdRegTimestamp	20240101-12:00:00.000
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
10	CheckSum	159

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 768 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
CollateralAssignment	AY	Optional	Optional	inside the TrdRegTimestamps component
CollateralInquiry	BB	Optional	Optional	inside the TrdRegTimestamps component
CollateralReport	BA	Optional	Optional	inside the TrdRegTimestamps component
CollateralRequest	AX	Optional	Optional	inside the TrdRegTimestamps component
CollateralResponse	AZ	Optional	Optional	inside the TrdRegTimestamps component
Confirmation	AK	Optional	Optional	inside the TrdRegTimestamps component
ExecutionReport	8	—	Optional	inside the TrdRegTimestamps component
NewOrderSingle	D	—	Optional	inside the TrdRegTimestamps component
OrderCancelReplaceRequest	G	—	Optional	inside the TrdRegTimestamps component
TradeCaptureReport	AE	Optional	Optional	inside the TrdRegTimestamps component
TradeCaptureReportAck	AR	Optional	Optional	inside the TrdRegTimestamps 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 768 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);// NoTrdRegTimestamps is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[768] is undefined.const entries = message.groups[768] ?? [];for (const entry of entries) {  // entry.fields is keyed by tag; entry.groups holds nested groups}

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