Every figure this model derived for WCT, 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 2025-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
0
PaymentsToAcquirePropertyPlantAndEquipment
2023-12-31
cash
2,805,408
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
5,762,306
AssetsCurrent
2025-12-31
current liabilities
1,255,767
LiabilitiesCurrent
2025-12-31
equity
11,151,170
StockholdersEquity
2025-12-31
interest expense
12,437
InterestExpenseNonoperating
2025-12-31
ocf
-6,317,821
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
1,348,084
Revenues
2025-12-31
sbc
1,085,333
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
WCT on one particular measure came for.
Ratio
Value
cash operating margin
-385.63
current ratio
5.01
current ratio reported
4.59
deferred revenue growth
-66.38
dilution pct
281.27
fcf margin
-468.65
growth cv
933.28
interest cover
-508.48
operating margin
-469.11
owner earnings margin
-549.16
revenue growth
-41.62
revenue growth per share
-84.69
roic
-57.02
rule of 40
-510.73
sbc pct revenue
80.51
What to be careful about
What this model itself distrusts about WCT's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current capital expenditure tagged (last tagged 2023-12-31); treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-06-30 (426 days old, balance sheet); 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 rests on 3 of 4 inputs; not tagged: sustained growth