biztrac. BETA
COMPANY REGISTER PROFILE
913893271 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

SOLHUS PARK AS

Org. no. 913893271 Limited company (AS) Stavanger Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 2.1m
Equity NOK 15.2m
Incorporated 2014
Share capital NOK 7.0m

SOLHUS PARK AS is registered as a limited company in Stavanger, Rogaland with organisation number 913893271. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 7.0m, divided into 1 shares. The company's stated purpose is: “Investere i fast eiendom, gjennom direkte investeringer eller via aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
▼ −32 %
Operating profit
NOK 2.1m
▲ +136 %
Equity
NOK 15.2m
▼ −16 %
Est. value
NOK 12.6m

Financial health · 2025

Liquidity
5.45
Very good
Current assets ÷ current liabilities
Profitability
5.2%
Weak
Return on total assets
Solidity
29.8%
Good
Equity as a share of total capital

Who owns SOLHUS PARK AS?

SOLHUS PARK AS
NOK 3.3m rev. · NOK 2.1m profit

SOLHUS PARK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLHUS PARK AS own?

SOLHUS PARK AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SOLHUS PARK AS

Who owns SOLHUS PARK AS?

Kåre Nilsen is the largest registered owner, with 100.0%.

What is the revenue of SOLHUS PARK AS?

SOLHUS PARK AS had revenue of NOK 3.3m in 2025.

Who is the general manager of SOLHUS PARK AS?

Kåre Nilsen is registered as general manager of SOLHUS PARK AS.

Where is SOLHUS PARK AS based?

SOLHUS PARK AS has its business address in Hundvåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.