RADIANT LOGISTICS, INC. (RLGT)

Every figure this model derived for RLGT, the value it took, and the element in the company's own XBRL it was read from — so any of it can be checked against the filing rather than taken on trust. As at 2026-03-31.

The figures, and where each came from

This is the part no other screener shows. Each figure below names the XBRL element it was read from, so it can be checked against the filing itself.

Figure	Value	XBRL tag	As at
capex	4,343,000	`PaymentsToAcquirePropertyPlantAndEquipment`	2026-03-31
cash	39,688,000	`CashAndCashEquivalentsAtCarryingValue`	2026-03-31
current assets	189,262,000	`AssetsCurrent`	2026-03-31
current liabilities	119,074,000	`LiabilitiesCurrent`	2026-03-31
equity	234,338,000	`StockholdersEquity`	2026-03-31
interest expense	2,285,000	`InterestExpenseNonoperating`	2026-03-31
ocf	32,545,000	`NetCashProvidedByUsedInOperatingActivities`	2026-03-31
revenue	893,500,000	`RevenueFromContractWithCustomerIncludingAssessedTax`	2026-03-31
sbc	1,870,000	`ShareBasedCompensation`	2026-03-31

The ratios

The figures themselves rather than their scores — what somebody looking up RLGT on one particular measure came for.

Ratio	Value
cash operating margin	3.39
current ratio	1.59
current ratio reported	1.59
dilution pct	-0.19
ebit cagr	-23.65
ebit yoy	2.75
fcf margin	3.16
growth cv	5.73
interest cover	9.33
operating margin	2.38
owner earnings margin	2.95
revenue growth	0.6
revenue growth per share	0.79
roic	8.6
rule of 40	2.99
sbc pct revenue	0.21

What to be careful about

What this model itself distrusts about RLGT's figures. Written by the derivation as it ran, not added afterwards.

no market cap; set `market_cap` in overrides.yaml
share count is from 2026-05-04 (118 days old, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
gross profit last tagged 2019-09-30 and no cost of sales line to rebuild it from; dropped from durability
no forward EPS estimate; growth rests on filings only. Analyst consensus is not published in XBRL, so it has to be fetched from a data provider or set by hand in overrides.yaml as `eps_growth_2y`
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev sales, ev owner earnings not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
durability DROPPED from the total: only 2 of 4 inputs could be computed (contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left