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

HOVDAN EIENDOM AS

Org. no. 984695780 Limited company (AS) Vestvågøy Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 763,000
Equity NOK 3.1m
Incorporated 2002
Share capital NOK 100,000

HOVDAN EIENDOM AS is registered as a limited company in Vestvågøy, Nordland with organisation number 984695780. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 763,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +2 %
Operating profit
NOK 763,000
▼ −28 %
Equity
NOK 3.1m
▼ −14 %
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
14.9%
Good
Return on total assets
Solidity
58.4%
Very good
Equity as a share of total capital

Who owns HOVDAN EIENDOM AS?

HOVDAN EIENDOM AS
NOK 1.7m rev. · NOK 763,000 profit

HOVDAN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOVDAN EIENDOM AS

Who owns HOVDAN EIENDOM AS?

VIKNA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HOVDAN EIENDOM AS?

HOVDAN EIENDOM AS had revenue of NOK 1.7m in 2025.

Who is the general manager of HOVDAN EIENDOM AS?

Fredrik Sigmund Qvigstad Williksen is registered as general manager of HOVDAN EIENDOM AS.

Where is HOVDAN EIENDOM AS based?

HOVDAN EIENDOM AS has its business address in Gravdal.

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.