Every figure this model derived for KUBR, 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-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
311,564
PaymentsToAcquireProductiveAssets
2024-12-31
cash
38,654
CashAndCashEquivalentsAtCarryingValue
2025-09-30
current assets
15,937,195
AssetsCurrent
2025-09-30
current liabilities
6,545,687
LiabilitiesCurrent
2025-09-30
equity
24,766,231
StockholdersEquity
2025-09-30
interest expense
23,002
InterestPaidNet
2025-09-30
ocf
-82,656
NetCashProvidedByUsedInOperatingActivities
2024-12-31
revenue
3,920,223
Revenues
2024-12-31
sbc
30,177
ShareBasedCompensation
2023-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
KUBR on one particular measure came for.
Ratio
Value
cash operating margin
60.39
current ratio
2.51
current ratio reported
2.43
deferred revenue growth
-33.33
dilution pct
-27.2
ebit yoy
-53.4
fcf margin
-10.06
growth cv
94.76
interest cover
82.69
operating margin
48.52
owner earnings margin
-10.83
revenue growth
74.29
revenue growth per share
139.42
roic
6.08
rule of 40
122.81
sbc pct revenue
0.77
What to be careful about
What this model itself distrusts about KUBR's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
revenue period ends 2024-12-31 (607 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 2025-11-19 (284 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 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
growth DROPPED from the total: only 2 of 4 inputs could be computed (sustained growth, margin trend not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, growth -- 45% of the model), so this row is not comparable with the others; its total rests on what was left