Every figure this model derived for MRT, 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
485,329
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
7,805,859
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
13,940,021
AssetsCurrent
2025-12-31
current liabilities
14,389,255
LiabilitiesCurrent
2025-12-31
equity
-67,087,884
StockholdersEquity
2025-12-31
interest expense
7,020,300
InterestPaidNet
2025-12-31
ocf
-14,781,252
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
39,241,487
Revenues
2025-12-31
sbc
11,280,399
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
MRT on one particular measure came for.
Ratio
Value
cash operating margin
-34.82
current ratio
1.14
current ratio reported
0.97
deferred revenue growth
15.4
dilution pct
32.39
fcf margin
-38.9
growth cv
1.57
interest cover
-4.06
operating margin
-72.71
owner earnings margin
-67.65
revenue growth
110.3
revenue growth per share
58.86
roic
-154.26
rule of 40
37.59
sbc pct revenue
28.75
What to be careful about
What this model itself distrusts about MRT'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.
gross profit not tagged; rebuilt from Revenues - CostOfRevenue
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