biztrac. BETA
COMPANY REGISTER PROFILE
989840231 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SOLKROKEN AUSTRHEIM AS

Org. no. 989840231 Limited company (AS) Øygarden Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −482,000
Equity NOK −1.1m
Incorporated 2006
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−482k kr).

SOLKROKEN AUSTRHEIM AS is registered as a limited company in Øygarden, Vestland with organisation number 989840231. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i og utvikling og drift av fast eiendom og det som står i forbindelse med dette, samt deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −482,000
▼ −151 %
Equity
NOK −1.1m
▼ −77 %

Financial health · 2025

Liquidity
6.67
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-160.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SOLKROKEN AUSTRHEIM AS?

SOLKROKEN AUSTRHEIM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLKROKEN AUSTRHEIM AS

Who owns SOLKROKEN AUSTRHEIM AS?

EINEVOLL INVEST AS is the largest registered owner, with 20.0%.

Who is the general manager of SOLKROKEN AUSTRHEIM AS?

Hallvar Einevoll is registered as general manager of SOLKROKEN AUSTRHEIM AS.

Where is SOLKROKEN AUSTRHEIM AS based?

SOLKROKEN AUSTRHEIM AS has its business address in Knarrevik.

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.