Every figure this model derived for AMST, 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
0
PaymentsToAcquirePropertyPlantAndEquipment
2024-06-30
cash
640,711
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
821,979
AssetsCurrent
2026-03-31
current liabilities
189,982
LiabilitiesCurrent
2026-03-31
equity
1,302,384
StockholdersEquity
2026-03-31
ocf
-1,925,451
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
341,437
Revenues
2026-03-31
sbc
480,983
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
AMST on one particular measure came for.
Ratio
Value
cash operating margin
-715.45
current ratio
4.42
current ratio reported
4.33
deferred revenue growth
3.65
dilution pct
38.7
fcf margin
-563.93
growth cv
2.25
operating margin
-863.74
owner earnings margin
-704.8
revenue growth
313.64
revenue growth per share
198.22
roic
-352.11
rule of 40
-550.1
sbc pct revenue
140.87
What to be careful about
What this model itself distrusts about AMST's figures. Written by the
derivation as it ran, not added afterwards.
no current capital expenditure tagged (last tagged 2024-06-30); treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-05-18 (104 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 debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 1M of net cash against a 2M annual burn is 0.3 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`
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: gross margin stability