Every figure this model derived for AMBR, 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-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
16,000
PaymentsToAcquirePropertyPlantAndEquipment
2024-12-31
cash
32,400,000
CashAndCashEquivalents
2025-06-30
current assets
175,414,000
CurrentAssets
2025-06-30
current liabilities
154,577,000
CurrentLiabilities
2025-06-30
equity
91,299,000
EquityAttributableToOwnersOfParent
2025-06-30
interest expense
511,000
InterestExpenseNonoperating
2024-12-31
ocf
-4,097,000
CashFlowsFromUsedInOperatingActivities
2025-06-30
revenue
35,903,000
RevenueFromContractsWithCustomers
2025-06-30
sbc
805,000
AdjustmentsForSharebasedPayments
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
AMBR on one particular measure came for.
Ratio
Value
cash operating margin
2.33
current ratio
1.2
current ratio reported
1.13
deferred revenue growth
-29.94
dilution pct
-10.37
fcf margin
-11.46
interest cover
0.06
operating margin
0.08
owner earnings margin
-13.7
revenue growth
1811.77
revenue growth per share
2032.96
rule of 40
1811.85
sbc pct revenue
2.24
What to be careful about
What this model itself distrusts about AMBR's figures. Written by the
derivation as it ran, not added afterwards.
only 180 days of filings, not a full year: margins and growth are measured, but return on capital and every enterprise-value multiple are refused rather than annualised
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 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.
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 rests on 4 of 5 inputs; not tagged: roic
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev ebit, 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