Every figure this model derived for MGA, 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.
The figures themselves rather than their scores — what somebody looking up
MGA on one particular measure came for.
Ratio
Value
cash operating margin
10.77
current ratio
1.3
current ratio reported
1.25
deferred revenue growth
50.83
dilution pct
-1.53
fcf margin
5.44
growth cv
1.1
interest cover
10.82
net debt ebitda
0.69
operating margin
7.08
owner earnings margin
5.44
revenue growth
-1.93
revenue growth per share
-0.4
roic
15.05
rule of 40
5.16
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about MGA's figures. Written by the
derivation as it ran, not added afterwards.
presents no operating result; summed as revenue minus the costs it does tag (CostOfGoodsAndServicesSold, SellingGeneralAndAdministrativeExpense, ResearchAndDevelopmentExpense). Checked against the company's own figures: the answer lands 4.0% of revenue from the 1,308M pre-tax profit it reports, which is its interest and other non-operating items
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged (last tagged 2011-12-31); treated as zero, so owner earnings are overstated
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.
gross profit not tagged; rebuilt from RevenueFromContractWithCustomerExcludingAssessedTax - CostOfGoodsAndServicesSold
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 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
2 of 5 dimensions could not be measured (valuation, growth -- 45% of the model), so this row is not comparable with the others; its total rests on what was left