Every figure this model derived for GSUN, 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-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
9,367
PaymentsToAcquirePropertyPlantAndEquipment
2025-09-30
cash
775,334
CashAndCashEquivalentsAtCarryingValue
2025-09-30
current assets
12,732,153
AssetsCurrent
2025-09-30
current liabilities
10,627,926
LiabilitiesCurrent
2025-09-30
equity
9,279,349
StockholdersEquity
2025-09-30
interest expense
340,474
InterestExpenseNonoperating
2025-09-30
ocf
-9,318,172
NetCashProvidedByUsedInOperatingActivities
2025-09-30
revenue
35,479,712
Revenues
2025-09-30
sbc
0
ShareBasedCompensation
2023-09-30
The ratios
The figures themselves rather than their scores — what somebody looking up
GSUN on one particular measure came for.
Ratio
Value
cash operating margin
-5.73
current ratio
2.09
current ratio reported
1.2
deferred revenue growth
-99.89
dilution pct
43.85
fcf margin
-26.29
growth cv
1.98
interest cover
-6.17
operating margin
-5.92
owner earnings margin
-26.29
revenue growth
482.83
revenue growth per share
305.18
roic
-13.58
rule of 40
476.91
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about GSUN'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 stock compensation tagged (last tagged 2023-09-30); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-09-30 (334 days old, weighted average diluted); 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