Every figure this model derived for JCTC, 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-05-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
21,628
PaymentsToAcquirePropertyPlantAndEquipment
2026-05-31
cash
1,063,801
CashAndCashEquivalentsAtCarryingValue
2026-05-31
current assets
15,327,471
AssetsCurrent
2026-05-31
current liabilities
10,602,275
LiabilitiesCurrent
2022-11-30
equity
14,774,357
StockholdersEquity
2026-05-31
interest expense
436,803
InterestPaidNet
2026-05-31
ocf
974,545
NetCashProvidedByUsedInOperatingActivities
2026-05-31
revenue
39,413,860
Revenues
2026-05-31
sbc
776
ShareBasedCompensation
2026-05-31
The ratios
The figures themselves rather than their scores — what somebody looking up
JCTC on one particular measure came for.
Ratio
Value
cash operating margin
-17.3
current ratio
1.45
current ratio reported
1.45
dilution pct
0.28
fcf margin
2.42
interest cover
-16.25
operating margin
-18.01
owner earnings margin
2.42
revenue growth
-10.71
revenue growth per share
-10.96
roic
-40.9
rule of 40
-28.72
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about JCTC's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
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 rests on 3 of 4 inputs; not tagged: contracted coverage