Every figure this model derived for REMEDY.HE, 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
cash
9,641,000
CashAndCashEquivalents
2026-01-01
current assets
44,797,000
CurrentAssets
2026-01-01
current liabilities
13,797,000
CurrentLiabilities
2026-01-01
equity
56,594,000
Equity
2026-01-01
interest expense
1,991,000
FinanceCosts
2025-12-31
ocf
4,513,000
CashFlowsFromUsedInOperatingActivities
2025-12-31
revenue
59,510,000
Revenue
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
REMEDY.HE on one particular measure came for.
Ratio
Value
cash operating margin
-24.98
current ratio
3.25
current ratio reported
3.25
ev owner earnings
54.47
ev sales
4.13
fcf margin
7.58
interest cover
-7.47
operating margin
-24.98
owner earnings margin
7.58
revenue growth
17.47
revenue growth per share
17.47
roic
-25.01
rule of 40
-7.51
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about REMEDY.HE'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; treated as zero, so owner earnings are overstated
no current capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
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 usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
there is no operating profit to value; valuation rests on EV/revenue (4.1x) instead
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`
durability DROPPED from the total: only 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth DROPPED from the total: only 1 of 4 inputs could be computed (sustained growth, margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (durability, growth -- 30% of the model), so this row is not comparable with the others; its total rests on what was left