Every figure this model derived for PAVS, 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
2026-03-31
cash
15,252,171
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
20,215,799
AssetsCurrent
2026-03-31
current liabilities
2,472,296
LiabilitiesCurrent
2026-03-31
equity
31,248,555
StockholdersEquity
2026-03-31
interest expense
262,514
InterestExpense
2026-03-31
ocf
-1,400,031
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
14,602,369
Revenues
2026-03-31
sbc
0
ShareBasedCompensation
2024-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
PAVS on one particular measure came for.
Ratio
Value
cash operating margin
-86.25
current ratio
8.18
current ratio reported
8.18
dilution pct
113.18
fcf margin
-9.59
growth cv
2.02
interest cover
-55.86
operating margin
-100.42
owner earnings margin
-9.59
revenue growth
20310.9
revenue growth per share
9474.56
roic
-72.42
rule of 40
20210.48
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about PAVS'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 (last tagged 2024-03-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-03-31 (152 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`
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