BIZTRAC BETA
Development of building projects

K2 BOLIG AS

Org. no. 917778493 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK −6.4m
Equity NOK 25.5m
Incorporated 2016
Share capital NOK 2.7m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6,4 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

K2 BOLIG AS is registered as a limited company in Stavanger, Rogaland with organisation number 917778493. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 2.7m, divided into 2666665 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom, primært for boligformål, og alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −6.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK −6.4m
Equity
NOK 25.5m
Est. value
NOK 23.3m

Financial health · 2024

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.7%
Good
Equity as a share of total capital

Who owns K2 BOLIG AS?

HELLAND AS
K2 BOLIG AS
NOK 2.4m rev. · NOK −6.4m profit

K2 BOLIG AS has 11 registered shareholders:

All shareholders and roles →

Which companies does K2 BOLIG AS own?

K2 BOLIG AS holds stakes in 15 companies:

See the full ownership structure →

Frequently asked questions about K2 BOLIG AS

Who owns K2 BOLIG AS?

HELLAND AS is the largest registered owner, with 17.7%.

What is the revenue of K2 BOLIG AS?

K2 BOLIG AS had revenue of NOK 2.4m in 2024.

Where is K2 BOLIG AS based?

K2 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.