Every figure this model derived for LGHL, 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 2025-12-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
11,480
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
20,124,296
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
26,234,458
AssetsCurrent
2025-12-31
current liabilities
6,383,863
LiabilitiesCurrent
2025-12-31
equity
25,634,651
StockholdersEquity
2025-12-31
interest expense
452,000
InterestExpenseDebt
2025-12-31
ocf
-3,523,695
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
9,390,651
Revenues
2025-12-31
sbc
214,893
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
LGHL on one particular measure came for.
Ratio
Value
cash operating margin
-25.14
current ratio
4.11
current ratio reported
4.11
fcf margin
-37.65
interest cover
-10.99
operating margin
-52.9
owner earnings margin
-39.93
revenue growth
-292.98
revenue growth per share
-292.98
roic
-16.67
rule of 40
-345.88
sbc pct revenue
2.29
What to be careful about
What this model itself distrusts about LGHL's figures. Written by the
derivation as it ran, not added afterwards.
operating income last tagged 2023-12-31, 731 days before the revenue period (2025-12-31); dropped rather than divided by current revenue
no operating income tagged; derived as revenue minus OperatingExpenses
revenue is annual, not TTM
operating income is annual, not TTM
no market cap; set `market_cap` in overrides.yaml
share count is from 2022-12-31 (1338 days old, weighted average diluted); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
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 rests on 3 of 4 inputs; not tagged: contracted coverage