BIZTRAC BETA
Retail sale of sports equipment

MO SPORT AS

Org. no. 985785236 Limited company (AS) Kvam Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 23.1m
Operating profit NOK 1.3m
Equity NOK 11.8m
Incorporated 2002
Employees 14
Share capital NOK 200,000

MO SPORT AS is registered as a limited company in Kvam, Vestland with organisation number 985785236. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2002 and has 14 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 23.1m
Operating profit
NOK 1.3m
Equity
NOK 11.8m
Est. value
NOK 12.3m

Financial health · 2025

Liquidity
2.99
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.4%
Very good
Equity as a share of total capital

Who owns MO SPORT AS?

GEIR MO HOLDING AS
MO SPORT AS
NOK 23.1m rev. · NOK 1.3m profit

MO SPORT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MO SPORT AS own?

MO SPORT AS holds a stake in 1 company:

See the full ownership structure →

Group structure

MO SPORT AS er morselskap for 2 datterselskaper:

Frequently asked questions about MO SPORT AS

Who owns MO SPORT AS?

GEIR MO HOLDING AS is the largest registered owner, with 75.0%.

What is the revenue of MO SPORT AS?

MO SPORT AS had revenue of NOK 23.1m in 2025.

Who is the general manager of MO SPORT AS?

Arve Øyri is registered as general manager of MO SPORT AS.

Where is MO SPORT AS based?

MO SPORT AS has its business address in Norheimsund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.