LegFactor (FIX tag 253)

floatFIX 4.4

LegFactor (tag 253) is a float field defined in FIX 4.4. It appears in 50 message types, always optionally.

At a glance

Tag
253
Name
LegFactor
Datatype
float
Dialects
FIX 4.4
Messages
50

What the specification says

Multileg instrument's individual leg security’s Factor. See Factor (228) field for description (Note tag # was reserved in FIX 4.1, added in FIX 4.3)

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

A real message using tag 253

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength179
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
555NoLegs2 entries2repeating group
600LegSymbolEXAMPLE
253LegFactor1.0
600LegSymbolEXAMPLE
253LegFactor1.0
10CheckSum192
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 253 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.

MessageMsgTypeRequirednessWhere in the message
Advertisement7Optionalinside InstrmtLegGrp › InstrumentLeg
AllocationInstructionJOptionalinside InstrmtLegGrp › InstrumentLeg
AllocationReportASOptionalinside InstrmtLegGrp › InstrumentLeg
AssignmentReportAWOptionalinside InstrmtLegGrp › InstrumentLeg
CollateralAssignmentAYOptionalinside InstrmtLegGrp › InstrumentLeg
CollateralInquiryBBOptionalinside InstrmtLegGrp › InstrumentLeg
CollateralInquiryAckBGOptionalinside InstrmtLegGrp › InstrumentLeg
CollateralReportBAOptionalinside InstrmtLegGrp › InstrumentLeg
CollateralRequestAXOptionalinside InstrmtLegGrp › InstrumentLeg
CollateralResponseAZOptionalinside InstrmtLegGrp › InstrumentLeg
ConfirmationAKOptionalinside InstrmtLegGrp › InstrumentLeg
CrossOrderCancelReplaceRequesttOptionalinside InstrmtLegGrp › InstrumentLeg
CrossOrderCancelRequestuOptionalinside InstrmtLegGrp › InstrumentLeg
DerivativeSecurityListAAOptionalinside RelSymDerivSecGrp › InstrmtLegGrp › InstrumentLeg
DontKnowTradeQOptionalinside InstrmtLegGrp › InstrumentLeg
EmailCOptionalinside InstrmtLegGrp › InstrumentLeg
ExecutionReport8Optionalinside InstrmtLegExecGrp › InstrumentLeg
IOI6Optionalinside InstrmtLegIOIGrp › InstrumentLeg
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › InstrmtLegGrp › InstrumentLeg
MarketDataRequestVOptionalinside InstrmtMDReqGrp › InstrmtLegGrp › InstrumentLeg
MarketDataSnapshotFullRefreshWOptionalinside InstrmtLegGrp › InstrumentLeg
MassQuoteiOptionalinside QuotSetGrp › QuotEntryGrp › InstrmtLegGrp › InstrumentLeg
MassQuoteAcknowledgementbOptionalinside QuotSetAckGrp › QuotEntryAckGrp › InstrmtLegGrp › InstrumentLeg
MultilegOrderCancelReplaceACOptionalinside LegOrdGrp › InstrumentLeg
NewOrderCrosssOptionalinside InstrmtLegGrp › InstrumentLeg
NewOrderMultilegABOptionalinside LegOrdGrp › InstrumentLeg
NewsBOptionalinside InstrmtLegGrp › InstrumentLeg
PositionMaintenanceReportAMOptionalinside InstrmtLegGrp › InstrumentLeg
PositionMaintenanceRequestALOptionalinside InstrmtLegGrp › InstrumentLeg
PositionReportAPOptionalinside InstrmtLegGrp › InstrumentLeg
QuoteSOptionalinside LegQuotGrp › InstrumentLeg
QuoteCancelZOptionalinside QuotCxlEntriesGrp › InstrmtLegGrp › InstrumentLeg
QuoteRequestROptionalinside QuotReqGrp › QuotReqLegsGrp › InstrumentLeg
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › QuotReqLegsGrp › InstrumentLeg
QuoteResponseAJOptionalinside LegQuotGrp › InstrumentLeg
QuoteStatusReportAIOptionalinside LegQuotStatGrp › InstrumentLeg
QuoteStatusRequestaOptionalinside InstrmtLegGrp › InstrumentLeg
RFQRequestAHOptionalinside RFQReqGrp › InstrmtLegGrp › InstrumentLeg
RequestForPositionsANOptionalinside InstrmtLegGrp › InstrumentLeg
RequestForPositionsAckAOOptionalinside InstrmtLegGrp › InstrumentLeg
SecurityDefinitiondOptionalinside InstrmtLegGrp › InstrumentLeg
SecurityDefinitionRequestcOptionalinside InstrmtLegGrp › InstrumentLeg
SecurityListyOptionalinside SecListGrp › InstrmtLegSecListGrp › InstrumentLeg
SecurityListRequestxOptionalinside InstrmtLegGrp › InstrumentLeg
SecurityStatusfOptionalinside InstrmtLegGrp › InstrumentLeg
SecurityStatusRequesteOptionalinside InstrmtLegGrp › InstrumentLeg
TradeCaptureReportAEOptionalinside TrdInstrmtLegGrp › InstrumentLeg
TradeCaptureReportAckAROptionalinside TrdInstrmtLegGrp › InstrumentLeg
TradeCaptureReportRequestADOptionalinside InstrmtLegGrp › InstrumentLeg
TradeCaptureReportRequestAckAQOptionalinside InstrmtLegGrp › InstrumentLeg

Wire format

A decimal number. The wire form keeps its trailing zeros, which is why decoders expose the raw string alongside the parsed number. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

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

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