NoHops (FIX tag 627)

NumInGroupFIX 4.4group countersession envelope

NoHops (tag 627) is a NumInGroup field defined in FIX 4.4. It belongs to the session envelope: every FIX 4.4 message carries it, so it identifies the session rather than describing the business event. 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: 627
Name: NoHops
Datatype: NumInGroup (int)
Dialects: FIX 4.4
Messages: 93

What the specification says

Number of HopCompID entries in repeating group.

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

A real message using tag 627

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	141
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
627	NoHops2 entries	2	repeating group
628	HopCompID	EXAMPLE
628	HopCompID	EXAMPLE
11	ClOrdID	ORD-10042
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	214

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 627 appears

Session envelope field

Tag 627 appears in every one of the 93 FIX 4.4 message types, because it is part of the standard header or trailer. Listing them all would say nothing useful — it is present on anything you will ever decode.

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