BIZTRAC BETA
Development of building projects

BIRKELANDSHAGEN AS

Org. no. 925758183 Limited company (AS) Hustadvika Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −167,000
Equity NOK −319,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−319k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−167k kr).

BIRKELANDSHAGEN AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 925758183. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikle eiendom, samt det som naturlig står i forbindelse med dette, herunder deltagelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −167,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −167,000
Equity
NOK −319,000

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-975.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BIRKELANDSHAGEN AS?

NORSK HOLDING AS
BIRKELANDSHAGEN AS
NOK 0 rev. · NOK −167,000 profit

BIRKELANDSHAGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIRKELANDSHAGEN AS

Who owns BIRKELANDSHAGEN AS?

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

What is the revenue of BIRKELANDSHAGEN AS?

BIRKELANDSHAGEN AS had revenue of NOK 0 in 2025.

Where is BIRKELANDSHAGEN AS based?

BIRKELANDSHAGEN AS has its business address in Elnesvågen.

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.