Every figure this model derived for NIVF, 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-12-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
135,025
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
758,621
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
7,383,571
AssetsCurrent
2025-12-31
current liabilities
2,366,351
LiabilitiesCurrent
2025-12-31
equity
26,631,519
StockholdersEquity
2025-12-31
interest expense
616,423
InterestExpenseDebt
2025-12-31
ocf
-10,926,056
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
4,726,433
Revenues
2025-12-31
sbc
0
ShareBasedCompensation
2022-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
NIVF on one particular measure came for.
Ratio
Value
cash operating margin
-222.97
current ratio
3.28
current ratio reported
3.12
deferred revenue growth
76.38
dilution pct
2750184.75
fcf margin
-234.03
growth cv
4.0
interest cover
-17.4
operating margin
-226.95
owner earnings margin
-234.03
revenue growth
-13.01
revenue growth per share
-100.0
roic
-32.43
rule of 40
-239.96
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about NIVF'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 2022-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 days old, balance sheet); 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