Every figure this model derived for LYEL, 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-06-30.
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
711,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-30
cash
204,102,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
213,541,000
AssetsCurrent
2026-06-30
current liabilities
39,867,000
LiabilitiesCurrent
2026-06-30
equity
233,815,000
StockholdersEquity
2026-06-30
ocf
-133,260,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
27,000
Revenues
2026-06-30
sbc
39,628,000
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
LYEL on one particular measure came for.
Ratio
Value
current ratio
5.36
current ratio reported
5.36
deferred revenue growth
-100.0
dilution pct
30.76
growth cv
2.76
revenue growth
-55.0
revenue growth per share
-65.59
roic
-681.96
rule of 40
-950036.48
What to be careful about
What this model itself distrusts about LYEL's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: operating margin, cash operating margin, sbc pct revenue, owner earnings margin, fcf margin, net margin, capex intensity, ocf margin, ebitda margin -- operating margin came out at -949,981% against a scale that tops out near 2,500%, which is arithmetic on a revenue figure of 27,000 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
no market cap; set `market_cap` in overrides.yaml
no debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 204M of net cash against a 134M annual burn is 1.5 years
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`
quality DROPPED from the total: only 1 of 5 inputs could be computed (operating margin, sbc discipline, owner earnings, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
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
3 of 5 dimensions could not be measured (quality, valuation, durability -- 65% of the model), so this row is not comparable with the others; its total rests on what was left