Every figure this model derived for JRSS, 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 2024-09-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.
The figures themselves rather than their scores — what somebody looking up
JRSS on one particular measure came for.
Ratio
Value
cash operating margin
-8.63
current ratio
0.8
current ratio reported
0.78
dilution pct
25.97
fcf margin
-27.74
growth cv
5.85
interest cover
-12.07
operating margin
-19.47
owner earnings margin
-37.17
sbc pct revenue
9.43
What to be careful about
What this model itself distrusts about JRSS's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2024-09-30 (1y old); this company's data is not usable and the scores below should be ignored
revenue period ends 2024-09-30 (699 days ago) - the tag chain found nothing recent, so treat this row as unscored
no market cap; set `market_cap` in overrides.yaml
share count is from 2024-09-30 (699 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.
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`
quality rests on 4 of 5 inputs; not tagged: roic
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: gross margin stability
growth rests on 3 of 4 inputs; not tagged: revenue growth