BIZTRAC BETA
COMPANY REGISTER PROFILE
986982132 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

SALEVIKEN AS

Org. no. 986982132 Limited company (AS) Sula Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −179,000
Equity NOK 6.5m
Incorporated 2004
Share capital NOK 317,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−179k kr).

SALEVIKEN AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 986982132. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2004. Registered share capital is NOK 317,000, divided into 317 shares. The company's stated purpose is: “Drive utleievirksomhet og eiendomsforvaltning som hovedaktivitet, samt enhver form for deltakelse i andre selskaper og annen virksomhet av økonomiskt art.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −179,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −179,000
Equity
NOK 6.5m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns SALEVIKEN AS?

ROLF SALEN
SALEVIKEN AS
NOK 0 rev. · NOK −179,000 profit

SALEVIKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALEVIKEN AS

Who owns SALEVIKEN AS?

ROLF SALEN is the largest registered owner, with 100.0%.

What is the revenue of SALEVIKEN AS?

SALEVIKEN AS had revenue of NOK 0 in 2024.

Who is the general manager of SALEVIKEN AS?

Rolf Salen is registered as general manager of SALEVIKEN AS.

Where is SALEVIKEN AS based?

SALEVIKEN AS has its business address in Langevåg.

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.