Every figure this model derived for AERTW, 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
1,133,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-30
cash
6,069,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
25,007,000
AssetsCurrent
2026-06-30
current liabilities
29,439,000
LiabilitiesCurrent
2026-06-30
equity
-2,799,000
StockholdersEquity
2026-06-30
interest expense
410,000
InterestExpense
2026-06-30
ocf
10,227,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
76,602,000
Revenues
2026-06-30
sbc
293,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
AERTW on one particular measure came for.
Ratio
Value
cash operating margin
10.71
current ratio
0.86
current ratio reported
0.85
deferred revenue growth
70.07
dilution pct
12.19
ebit cagr
40.61
fcf margin
11.87
growth cv
1.64
interest cover
17.21
operating margin
9.21
owner earnings margin
11.49
revenue growth
11.24
revenue growth per share
-0.85
rule of 40
20.45
sbc pct revenue
0.38
What to be careful about
What this model itself distrusts about AERTW'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 2025-07-01 (425 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.
invested capital is -7M (cash exceeds equity plus debt), so return on capital is unbounded rather than undefined; scored as maximal
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
growth rests on 3 of 4 inputs; not tagged: sustained growth