QMMM Holdings Ltd
QMMMdata completeness 75%3 fiscal years on fileData notes: no data for concept 'totalDebt'; no data for concept 'interestExpense'
QMMM Holdings Ltd earns about 94% on invested capital, but has diluted owners by 3% over 3 years — worth asking whether the growth reaches owners. The cash-flow models don't apply cleanly here — the ledger says why below.Whether it’s worth owning at today’s price is the last question — and yours to answer, below.
| Figure | FY 2022 | FY 2023 | FY 2024 |
|---|---|---|---|
| Revenue | $3.4M1 | $2.81M1 | $2.7M1 |
| Net income | $800,5632 | −$1.29M2 | −$1.58M2 |
| Operating cash flow | $638,1863 | −$1.13M3 | −$6.25M3 |
| Capital expenditure | $36,2694 | $12,3354 | — |
| Free cash flow (derived) | $601,9173 | −$1.15M3 | — |
| Total debt | — | — | — |
| Cash & equivalents | — | $130,2015 | $497,9935 |
| Diluted shares | 15.0M | 15.0M | 15.4M |
Superscripts are receipts. Each links to the SEC filing the number came from (full list at the bottom).
10 shares is a claim on $3.43 of net worth that earned you −$1.02 last year.
It earned an average 94% on invested capital over 3 years. Compare that to what it costs to fund the business.
seeing a moat in the numbers →Share count is up 3% over 3 years — owners have been diluted. Worth asking what they got for it.
reading capital allocation →Signals, not verdicts — read from the filings above. Numbers don’t prove a moat; they show its footprint. You decide.
Different models answer different questions — which to trust when →
- 20-F · period ending 2022-09-30 · accession 0001493152-25-003751 (RevenueFromContractWithCustomerExcludingAssessedTax)
- 20-F · period ending 2022-09-30 · accession 0001493152-25-003751 (NetIncomeLoss)
- 20-F · period ending 2022-09-30 · accession 0001493152-25-003751 (NetCashProvidedByUsedInOperatingActivities)
- 20-F · period ending 2022-09-30 · accession 0001493152-25-003751 (PaymentsToAcquirePropertyPlantAndEquipment)
- 20-F · period ending 2023-09-30 · accession 0001493152-25-003751 (CashAndCashEquivalentsAtCarryingValue)