Every figure this model derived for CLGN, 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
28,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
5,591,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
6,747,000
AssetsCurrent
2025-12-31
current liabilities
2,672,000
LiabilitiesCurrent
2025-12-31
equity
6,081,000
StockholdersEquity
2025-12-31
ocf
-9,419,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
2,371,000
Revenues
2025-12-31
sbc
999,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
CLGN on one particular measure came for.
Ratio
Value
cash operating margin
-403.71
current ratio
2.53
current ratio reported
2.53
deferred revenue growth
-84.54
dilution pct
6.54
fcf margin
-398.44
growth cv
1.81
operating margin
-484.31
owner earnings margin
-440.57
revenue growth
360.39
revenue growth per share
332.11
roic
-1851.34
rule of 40
-123.92
sbc pct revenue
42.13
What to be careful about
What this model itself distrusts about CLGN's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 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 debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 6M of net cash against a 9M annual burn is 0.6 years
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