Every figure this model derived for MSGY, 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-03-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
1,972,308
PaymentsToAcquirePropertyPlantAndEquipment
2026-03-31
cash
315,721
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
9,056,515
AssetsCurrent
2026-03-31
current liabilities
2,895,083
LiabilitiesCurrent
2026-03-31
equity
8,363,242
StockholdersEquity
2026-03-31
ocf
-3,813,420
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
23,555,839
Revenues
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
MSGY on one particular measure came for.
Ratio
Value
cash operating margin
-32.33
current ratio
4.48
current ratio reported
3.13
dilution pct
16.76
fcf margin
-24.56
growth cv
1.25
operating margin
-33.17
owner earnings margin
-24.56
revenue growth
1.02
revenue growth per share
-13.48
roic
-76.7
rpo growth
111.13
rule of 40
-32.15
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about MSGY'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; treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-03-31 (152 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: 0M of net cash against a 6M annual burn is 0.1 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
growth rests on 3 of 4 inputs; not tagged: sustained growth