Every figure this model derived for CHR, 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
1,000
PaymentsToAcquirePropertyPlantAndEquipment
2024-12-31
cash
243,814,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
366,585,000
AssetsCurrent
2025-12-31
current liabilities
31,789,000
LiabilitiesCurrent
2025-12-31
equity
369,683,000
StockholdersEquity
2025-12-31
interest expense
366,000
InterestExpenseDebt
2025-12-31
ocf
17,939,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
148,835,000
Revenues
2025-12-31
sbc
0
ShareBasedCompensation
2022-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
CHR on one particular measure came for.
Ratio
Value
cash operating margin
22.29
current ratio
11.53
current ratio reported
11.53
deferred revenue growth
-96.3
dilution pct
415.93
ebit cagr
-7.74
ebit yoy
2.72
fcf margin
12.05
growth cv
2.38
interest cover
71.83
operating margin
17.66
owner earnings margin
12.05
revenue growth
1.11
revenue growth per share
-80.4
roic
16.5
rule of 40
18.78
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about CHR's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged (last tagged 2022-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 days old, weighted average diluted); 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 - CostOfRevenue
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