BIZTRAC BETA
Rental and operating of own or leased real estate

BIRGER HATLEBAKKS VEG 17 AS

Org. no. 987563621 Limited company (AS) Ålesund Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 6.4m
Operating profit NOK 2.4m
Equity NOK 21.5m
Incorporated 2004
Share capital NOK 8.0m

BIRGER HATLEBAKKS VEG 17 AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 987563621. 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 8.0m, divided into 133333 shares. The company's stated purpose is: “Utvikling og forvaltning av eiendommen Birger Hatlebakks veg 17.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.4m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 6.4m
Operating profit
NOK 2.4m
Equity
NOK 21.5m
Est. value
NOK 18.7m

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.5%
Satisfactory
Equity as a share of total capital

Who owns BIRGER HATLEBAKKS VEG 17 AS?

S.G. INVEST AS
BIRGER HATLEBAKKS VEG 17 AS
NOK 6.4m rev. · NOK 2.4m profit

BIRGER HATLEBAKKS VEG 17 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIRGER HATLEBAKKS VEG 17 AS

Who owns BIRGER HATLEBAKKS VEG 17 AS?

S.G. INVEST AS is the largest registered owner, with 37.5%.

What is the revenue of BIRGER HATLEBAKKS VEG 17 AS?

BIRGER HATLEBAKKS VEG 17 AS had revenue of NOK 6.4m in 2025.

Who is the general manager of BIRGER HATLEBAKKS VEG 17 AS?

Ove Bjørkavåg is registered as general manager of BIRGER HATLEBAKKS VEG 17 AS.

Where is BIRGER HATLEBAKKS VEG 17 AS based?

BIRGER HATLEBAKKS VEG 17 AS has its business address in Ålesund.

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.