Every figure this model derived for MPT, 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
cash
425,001,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
equity
4,544,705,000
StockholdersEquity
2026-03-31
interest expense
527,891,000
InterestExpense
2026-03-31
ocf
216,124,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
1,000,288,000
Revenues
2026-03-31
sbc
25,746,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
MPT on one particular measure came for.
Ratio
Value
cash operating margin
34.82
dilution pct
0.11
ebit cagr
-56.94
fcf margin
21.61
interest cover
0.08
net debt ebitda
28.64
operating margin
4.18
owner earnings margin
19.03
revenue growth
5.51
revenue growth per share
5.4
roic
0.24
rule of 40
9.69
sbc pct revenue
2.57
What to be careful about
What this model itself distrusts about MPT's figures. Written by the
derivation as it ran, not added afterwards.
operating income last tagged 2017-12-31, 3012 days before the revenue period (2026-03-31); dropped rather than divided by current revenue
no operating income tagged; derived as revenue minus CostsAndExpenses
no current capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-05-06 (116 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.
gross profit not tagged; rebuilt from Revenues - CostOfGoodsAndServicesSold
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
resilience rests on 2 of 3 inputs; not tagged: liquidity