Every figure this model derived for PLGO, 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-06-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
1,400,000
PaymentsToAcquireProductiveAssets
2026-06-30
cash
444,300,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
equity
2,220,500,000
StockholdersEquity
2026-06-30
interest expense
42,600,000
InterestPaidNet
2025-12-31
ocf
631,500,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
2,513,400,000
Revenues
2026-06-30
sbc
10,200,000
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
PLGO on one particular measure came for.
Ratio
Value
cash operating margin
18.13
dilution pct
-7.69
ebit cagr
64.83
fcf margin
25.07
growth cv
1.89
interest cover
10.79
net debt ebitda
0.62
operating margin
18.29
owner earnings margin
24.66
revenue growth
-3.61
revenue growth per share
4.42
roic
14.55
rule of 40
14.68
sbc pct revenue
0.41
What to be careful about
What this model itself distrusts about PLGO's figures. Written by the
derivation as it ran, not added afterwards.
no operating income tagged; derived as revenue minus BenefitsLossesAndExpenses
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 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 DROPPED from the total: only 2 of 4 inputs could be computed (contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
resilience rests on 2 of 3 inputs; not tagged: liquidity
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left