biztrac. BETA
COMPANY REGISTER PROFILE
918112278 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

HAGA BOLIG AS

Org. no. 918112278 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 251.2m
Operating profit NOK 36.0m
Equity NOK 38.4m
Incorporated 2016
Employees 12
Share capital NOK 1.0m

HAGA BOLIG AS is registered as a limited company in Stavanger, Rogaland with organisation number 918112278. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016 and has 12 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utvikling av eiendommer og annet som naturlig faller sammen med dette. Selskapet kan delta i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 251.2m in revenue and NOK 36.0m in operating profit.

Key figures · 2025

Revenue
NOK 251.2m
▲ +83 %
Operating profit
NOK 36.0m
▲ +35 %
Equity
NOK 38.4m
▲ +37 %
Est. value
NOK 101.6m

Financial health · 2025

Liquidity
2.25
Very good
Current assets ÷ current liabilities
Profitability
28.8%
Very good
Return on total assets
Solidity
22.9%
Good
Equity as a share of total capital

Who owns HAGA BOLIG AS?

HAGA BOLIG AS
NOK 251.2m rev. · NOK 36.0m profit

HAGA BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAGA BOLIG AS

Who owns HAGA BOLIG AS?

T. HAGA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HAGA BOLIG AS?

HAGA BOLIG AS had revenue of NOK 251.2m in 2025.

Who is the general manager of HAGA BOLIG AS?

Tommy Haga is registered as general manager of HAGA BOLIG AS.

Where is HAGA BOLIG AS based?

HAGA BOLIG AS has its business address in Stavanger.

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.