Every figure this model derived for SIGY, 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 2020-09-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
0
PaymentsToAcquirePropertyPlantAndEquipment
2022-12-31
cash
85,571
CashAndCashEquivalentsAtCarryingValue
2025-09-30
current assets
85,571
AssetsCurrent
2025-09-30
current liabilities
3,989,491
LiabilitiesCurrent
2025-09-30
equity
-5,917,209
StockholdersEquity
2025-09-30
revenue
9,929
Revenues
2020-09-30
sbc
0
ShareBasedCompensation
2025-09-30
The ratios
The figures themselves rather than their scores — what somebody looking up
SIGY on one particular measure came for.
Ratio
Value
current ratio
0.02
current ratio reported
0.02
growth cv
1.91
revenue growth
-92.8
revenue growth per share
-92.8
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about SIGY's figures. Written by the
derivation as it ran, not added afterwards.
operating income last tagged 2025-09-30, -1826 days before the revenue period (2020-09-30); dropped rather than divided by current revenue
operating cash flow last tagged 2025-09-30, -1826 days before the revenue period (2020-09-30); dropped rather than divided by current revenue
revenue period ends 2020-09-30 (2160 days ago) - the tag chain found nothing recent, so treat this row as unscored
no current stock compensation tagged (last tagged 2025-09-30); treated as zero, so owner earnings are overstated
no current capital expenditure tagged (last tagged 2022-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-11-14 (289 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 usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
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`
quality DROPPED from the total: only 1 of 5 inputs could be computed (operating margin, roic, owner earnings, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev ebit, 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
resilience rests on 2 of 3 inputs; not tagged: interest cover
growth DROPPED from the total: only 2 of 4 inputs could be computed (margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (quality, valuation, growth -- 75% of the model), so this row is not comparable with the others; its total rests on what was left
no interest expense tagged while 4M of debt is on the balance sheet, so interest cover is unmeasured rather than perfect