Every figure this model derived for CITR, 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-06-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
193,953
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
2,519,302
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
3,682,667
AssetsCurrent
2026-06-30
current liabilities
420,088
LiabilitiesCurrent
2026-06-30
equity
9,012,862
StockholdersEquity
2026-06-30
interest expense
716,435
InterestExpense
2026-06-30
ocf
-7,786,108
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
1,349,968
Revenues
2026-06-30
sbc
10,028,600
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
CITR on one particular measure came for.
Ratio
Value
cash operating margin
-555.97
current ratio
9.24
current ratio reported
8.77
deferred revenue growth
-77.45
fcf margin
-591.13
growth cv
0.89
interest cover
-25.07
operating margin
-1330.49
owner earnings margin
-1334.01
revenue growth
-26.38
revenue growth per share
-26.38
roic
-215.82
rule of 40
-1356.87
sbc pct revenue
742.88
What to be careful about
What this model itself distrusts about CITR's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: net margin -- net margin came out at -1,788% against a scale that tops out near 1,500%, which is arithmetic on a revenue figure of 1,349,968 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
no market cap; set `market_cap` in overrides.yaml
diluted share count moved +48% in a year (8M to 12M, a ratio of 1.48), which is a stock split rather than issuance; growth is measured on total revenue, not per share
gross profit not tagged since 2024-03-31; rebuilt from Revenues - CostOfRevenue
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 rests on 3 of 4 inputs; not tagged: sustained growth