Every figure this model derived for OKMN, 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
cash
24,333
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
35,357
AssetsCurrent
2026-03-31
current liabilities
691,027
LiabilitiesCurrent
2026-03-31
equity
-585,617
StockholdersEquity
2026-03-31
interest expense
20,883
InterestExpenseNonoperating
2026-03-31
ocf
-124,353
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
13,538
Revenues
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
OKMN on one particular measure came for.
Ratio
Value
current ratio
0.05
current ratio reported
0.05
dilution pct
0.67
fcf margin
-918.55
interest cover
-27.03
owner earnings margin
-918.55
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about OKMN's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: operating margin, cash operating margin, net margin, ebitda margin -- operating margin came out at -4,169% against a scale that tops out near 2,500%, which is arithmetic on a revenue figure of 13,538 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no current capital expenditure tagged; 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-15 (107 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 DROPPED from the total: only 2 of 5 inputs could be computed (operating margin, roic, 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 rests on 3 of 4 inputs; not tagged: contracted coverage
growth DROPPED from the total: only 2 of 4 inputs could be computed (revenue growth, sustained growth 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, growth -- 75% of the model), so this row is not comparable with the others; its total rests on what was left