BIZTRAC BETA
Other captive investment companies

OEMS AS

Org. no. 919062975 Limited company (AS) Ålesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 774,000
Incorporated 2017
Share capital NOK 440,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

OEMS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 919062975. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 440,000, divided into 400 shares. The company's stated purpose is: “Å kjøpe, eie, salg og forvaltning av aksjer, selskapsandeler og dertil tilhørende aktiviteter. Selskapet kan videre delta i andre selskaper med samme eller lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 774,000
Est. value
NOK 707,000

Financial health · 2024

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

Who owns OEMS AS?

ODD ERIK MOA SØVIK
OEMS AS
NOK 0 rev. · NOK −2,000 profit

OEMS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OEMS AS own?

OEMS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OEMS AS

Who owns OEMS AS?

ODD ERIK MOA SØVIK is the largest registered owner, with 100.0%.

What is the revenue of OEMS AS?

OEMS AS had revenue of NOK 0 in 2025.

Who is the general manager of OEMS AS?

Odd Erik Moa Søvik is registered as general manager of OEMS AS.

Where is OEMS AS based?

OEMS AS has its business address in Ålesund.

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.