Every figure this model derived for PDC, 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-04-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
3,052
PaymentsToAcquirePropertyPlantAndEquipment
2025-04-30
cash
753,529
CashAndCashEquivalentsAtCarryingValue
2025-04-30
current assets
1,004,954
AssetsCurrent
2025-04-30
current liabilities
579,217
LiabilitiesCurrent
2025-04-30
equity
519,020
StockholdersEquity
2025-04-30
interest expense
12,416
InterestExpense
2025-04-30
ocf
-1,344,274
NetCashProvidedByUsedInOperatingActivities
2025-04-30
revenue
3,087,437
Revenues
2025-04-30
sbc
10,261
ShareBasedCompensation
2024-04-30
The ratios
The figures themselves rather than their scores — what somebody looking up
PDC on one particular measure came for.
Ratio
Value
cash operating margin
-55.04
current ratio
1.78
current ratio reported
1.74
dilution pct
2.12
fcf margin
-43.64
interest cover
-138.83
operating margin
-55.83
owner earnings margin
-43.97
revenue growth
171.19
revenue growth per share
165.57
roic
-630.21
rule of 40
115.36
sbc pct revenue
0.33
What to be careful about
What this model itself distrusts about PDC's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2025-04-30 (1y old); this company's data is not usable and the scores below should be ignored
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2025-04-30 (487 days ago) - the tag chain found nothing recent, so treat this row as unscored
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-04-30 (487 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: worst year
growth rests on 3 of 4 inputs; not tagged: sustained growth