Every figure this model derived for UDR, 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
capex
0
PaymentsToAcquireProductiveAssets
2019-03-31
cash
1,300,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
equity
3,285,680,000
StockholdersEquity
2026-03-31
interest expense
197,494,000
InterestExpenseDebt
2026-03-31
ocf
875,414,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
1,716,218,000
Revenues
2026-03-31
sbc
28,554,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
UDR on one particular measure came for.
Ratio
Value
cash operating margin
79.59
dilution pct
0.28
ebit cagr
34.79
ebit yoy
102.2
fcf margin
51.01
growth cv
0.83
interest cover
3.35
net debt ebitda
4.23
operating margin
38.53
owner earnings margin
49.34
revenue growth
2.15
revenue growth per share
1.86
roic
5.84
rule of 40
40.67
sbc pct revenue
1.66
What to be careful about
What this model itself distrusts about UDR's figures. Written by the
derivation as it ran, not added afterwards.
no current capital expenditure tagged (last tagged 2019-03-31); 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-04-27 (125 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