BIZTRAC BETA
Rental and operating of own or leased real estate

GRØNVIKA EIENDOM AS

Org. no. 993371556 Limited company (AS) Ålesund Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 150,000
Operating profit NOK 88,000
Equity NOK 990,000
Incorporated 2008
Share capital NOK 190,000

GRØNVIKA EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 993371556. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 190,000, divided into 190 shares. The company's stated purpose is: “Erverv og forvaltning av fast eiendom. Selskapet skal også ved aksjetegning eller på annen måte kunne gjøre seg interessert i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 150,000 in revenue and NOK 88,000 in operating profit.

Key figures · 2025

Revenue
NOK 150,000
Operating profit
NOK 88,000
Equity
NOK 990,000
Est. value
NOK 825,000

Financial health · 2025

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

Who owns GRØNVIKA EIENDOM AS?

ELDAR PATRICH HÅHJEM
GRØNVIKA EIENDOM AS
NOK 150,000 rev. · NOK 88,000 profit

GRØNVIKA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRØNVIKA EIENDOM AS

Who owns GRØNVIKA EIENDOM AS?

ELDAR PATRICH HÅHJEM is the largest registered owner, with 50.0%.

What is the revenue of GRØNVIKA EIENDOM AS?

GRØNVIKA EIENDOM AS had revenue of NOK 150,000 in 2025.

Who is the general manager of GRØNVIKA EIENDOM AS?

Eldar Patrich Håhjem is registered as general manager of GRØNVIKA EIENDOM AS.

Where is GRØNVIKA EIENDOM AS based?

GRØNVIKA EIENDOM AS has its business address in Skodje.

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.