Every figure this model derived for VRDR, 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
378
PaymentsToAcquirePropertyPlantAndEquipment
2025-06-30
cash
3,406,060
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
3,121,083
AssetsCurrent
2026-03-31
current liabilities
875,419
LiabilitiesCurrent
2026-03-31
equity
38,006,630
StockholdersEquity
2026-03-31
interest expense
1,343
InterestExpense
2025-12-31
ocf
-2,907,503
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
12,157
Revenues
2025-12-31
sbc
89,165
ShareBasedCompensation
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
VRDR on one particular measure came for.
Ratio
Value
current ratio
3.57
current ratio reported
3.57
dilution pct
4.59
growth cv
33.86
interest cover
-3279.01
revenue growth
-94.39
revenue growth per share
-94.64
roic
-10.05
rule of 40
-36318.03
sbc pct revenue
733.45
What to be careful about
What this model itself distrusts about VRDR's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: operating margin, cash operating margin, owner earnings margin, fcf margin, net margin, ocf margin, ebitda margin -- operating margin came out at -36,224% against a scale that tops out near 2,500%, which is arithmetic on a revenue figure of 12,157 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-05-12 (110 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, owner earnings, 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 rests on 3 of 4 inputs; not tagged: sustained growth
2 of 5 dimensions could not be measured (quality, valuation -- 55% of the model), so this row is not comparable with the others; its total rests on what was left