BIZTRAC BETA
Retail sale of automotive fuel

MO AUTO HOLDING AS

Org. no. 965622578 Limited company (AS) Kvam Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 160,000
Operating profit NOK −23,000
Equity NOK 3.3m
Incorporated 1992
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MO AUTO HOLDING AS is registered as a limited company in Kvam, Vestland with organisation number 965622578. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 1992. Registered share capital is NOK 100,000. The company's stated purpose is: “Eige aksjar.”. The most recent filed accounts, for the 2024 financial year, show NOK 160,000 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 160,000
Operating profit
NOK −23,000
Equity
NOK 3.3m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns MO AUTO HOLDING AS?

SVEIN HOGNE BØRVEN
MO AUTO HOLDING AS
NOK 160,000 rev. · NOK −23,000 profit

MO AUTO HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MO AUTO HOLDING AS own?

MO AUTO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MO AUTO HOLDING AS

Who owns MO AUTO HOLDING AS?

SVEIN HOGNE BØRVEN is the largest registered owner, with 50.0%.

What is the revenue of MO AUTO HOLDING AS?

MO AUTO HOLDING AS had revenue of NOK 160,000 in 2024.

Where is MO AUTO HOLDING AS based?

MO AUTO HOLDING 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.