BIZTRAC BETA
Business and other management consultancy activities

SVEEN INV AS

Org. no. 971580569 Limited company (AS) Molde Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 69,000
Operating profit NOK 3,000
Equity NOK 12.3m
Incorporated 1994
Share capital NOK 200,000

SVEEN INV AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 971580569. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1994. Registered share capital is NOK 200,000. The company's stated purpose is: “Delta i andre selskaper og å drive salg av EDB produkter, tjenester relatert til regnskapsbyrå- bransjen, og regnskapstjenester. Investere i andre selskaper, eiendom og andre investeringer, samt utleie og finansiering. Gjennomføre aktivitet som dertil er naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 69,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 69,000
Operating profit
NOK 3,000
Equity
NOK 12.3m
Est. value
NOK 6.1m

Financial health · 2024

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

Who owns SVEEN INV AS?

ANDREAS NISTAD
SVEEN INV AS
NOK 69,000 rev. · NOK 3,000 profit

SVEEN INV AS has 6 registered shareholders:

All shareholders and roles →

Which companies does SVEEN INV AS own?

SVEEN INV AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SVEEN INV AS

Who owns SVEEN INV AS?

ANDREAS NISTAD is the largest registered owner, with 20.0%.

What is the revenue of SVEEN INV AS?

SVEEN INV AS had revenue of NOK 69,000 in 2024.

Where is SVEEN INV AS based?

SVEEN INV AS has its business address in Molde.

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.