Every figure this model derived for OST, 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-09-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
7,202,097
PaymentsToAcquirePropertyPlantAndEquipment
2025-09-30
cash
5,074,702
CashAndCashEquivalentsAtCarryingValue
2025-09-30
current assets
18,374,551
AssetsCurrent
2025-09-30
current liabilities
39,735,454
LiabilitiesCurrent
2025-09-30
equity
6,999,814
StockholdersEquity
2025-09-30
interest expense
141,879
InterestExpense
2025-09-30
ocf
85,245
NetCashProvidedByUsedInOperatingActivities
2025-09-30
revenue
39,678,541
Revenues
2025-09-30
The ratios
The figures themselves rather than their scores — what somebody looking up
OST on one particular measure came for.
Ratio
Value
cash operating margin
-17.09
current ratio
0.46
current ratio reported
0.46
dilution pct
3734.8
fcf margin
-17.94
interest cover
-63.97
operating margin
-22.88
owner earnings margin
-17.94
revenue growth
22.23
revenue growth per share
-96.81
roic
-166.25
rule of 40
-0.65
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about OST's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-09-30 (334 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 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