BIZTRAC BETA
Rental and operating of own or leased real estate

SOLAKROSSEN 14 AS

Org. no. 818086032 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 2.0m
Equity NOK 1.3m
Incorporated 2016
Share capital NOK 175,000

SOLAKROSSEN 14 AS is registered as a limited company in Stavanger, Rogaland with organisation number 818086032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 175,000, divided into 3500 shares. The company's stated purpose is: “Selskapets formål er å utvikle og forvalte Det Norske Misjonsselskaps eiendomsvirksomhet, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 2.0m
Equity
NOK 1.3m
Est. value
NOK 4.3m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.1%
Weak
Equity as a share of total capital

Who owns SOLAKROSSEN 14 AS?

NMS EIENDOMMER AS
SOLAKROSSEN 14 AS
NOK 2.8m rev. · NOK 2.0m profit

SOLAKROSSEN 14 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SOLAKROSSEN 14 AS er morselskap for 5 datterselskaper:

Frequently asked questions about SOLAKROSSEN 14 AS

Who owns SOLAKROSSEN 14 AS?

NMS EIENDOMMER AS is the largest registered owner, with 100.0%.

What is the revenue of SOLAKROSSEN 14 AS?

SOLAKROSSEN 14 AS had revenue of NOK 2.8m in 2024.

Who is the general manager of SOLAKROSSEN 14 AS?

Pelle Per Kristian Ueland Wister is registered as general manager of SOLAKROSSEN 14 AS.

Where is SOLAKROSSEN 14 AS based?

SOLAKROSSEN 14 AS has its business address in Stavanger.

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.