Every figure this model derived for RENT, 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-04-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
71,800,000
PaymentsToAcquireOtherProductiveAssets
2026-04-30
cash
37,100,000
CashAndCashEquivalentsAtCarryingValue
2026-04-30
current assets
54,700,000
AssetsCurrent
2026-04-30
current liabilities
72,800,000
LiabilitiesCurrent
2026-04-30
equity
-53,300,000
StockholdersEquity
2026-04-30
interest expense
0
InterestPaidNet
2026-01-31
ocf
-8,600,000
NetCashProvidedByUsedInOperatingActivities
2026-04-30
revenue
350,100,000
Revenues
2026-04-30
sbc
4,200,000
ShareBasedCompensation
2026-04-30
The ratios
The figures themselves rather than their scores — what somebody looking up
RENT on one particular measure came for.
Ratio
Value
cash operating margin
-12.82
current ratio
0.94
current ratio reported
0.75
deferred revenue growth
20.0
fcf margin
-22.96
growth cv
1.02
operating margin
-16.42
owner earnings margin
-24.16
revenue growth
16.39
revenue growth per share
16.39
roic
-68.1
rule of 40
-0.03
sbc pct revenue
1.2
What to be careful about
What this model itself distrusts about RENT's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-04-30 (122 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.
diluted share count moved +203% in a year (4M to 12M, a ratio of 3.02), which is a stock split rather than issuance; growth is measured on total revenue, not per share
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