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

HOVDEGREND AS

Org. no. 986961259 Limited company (AS) Bykle Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 51.7m
Operating profit NOK 12.2m
Equity NOK 9.6m
Incorporated 2004
Share capital NOK 88,000

HOVDEGREND AS is registered as a limited company in Bykle, Agder with organisation number 986961259. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 88,000, divided into 87590 shares. The company's stated purpose is: “Turistrelatert utleievirksomhet, eiendomsutvikling, deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 51.7m in revenue and NOK 12.2m in operating profit.

Key figures · 2025

Revenue
NOK 51.7m
Operating profit
NOK 12.2m
▲ +32644 %
Equity
NOK 9.6m
▲ +2563 %
Est. value
NOK 44.0m

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
9.6%
Satisfactory
Return on total assets
Solidity
5.9%
Weak
Equity as a share of total capital

Who owns HOVDEGREND AS?

HOVDEGREND AS
NOK 51.7m rev. · NOK 12.2m profit

HOVDEGREND AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HOVDEGREND AS er morselskap for 4 datterselskaper:

Frequently asked questions about HOVDEGREND AS

Who owns HOVDEGREND AS?

BRØDR. BREIVEGEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HOVDEGREND AS?

HOVDEGREND AS had revenue of NOK 51.7m in 2025.

Who is the general manager of HOVDEGREND AS?

Jo Breivegen is registered as general manager of HOVDEGREND AS.

Where is HOVDEGREND AS based?

HOVDEGREND AS has its business address in Hovden I Setesdal.

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.