BIZTRAC BETA
Development of building projects

ALKA EIENDOM AS

Org. no. 998526728 Limited company (AS) Vestby Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 166,000
Operating profit NOK 49,000
Equity NOK 464,000
Incorporated 2012
Share capital NOK 30,000

ALKA EIENDOM AS is registered as a limited company in Vestby, Akershus with organisation number 998526728. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bygg og anleggsvirksomhet, eiendomsutvikling, deltagelse i andre selskaper samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 166,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 166,000
Operating profit
NOK 49,000
Equity
NOK 464,000
Est. value
NOK 401,000

Financial health · 2024

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

Who owns ALKA EIENDOM AS?

KJELL ARNE BJØRNERUD
ALKA EIENDOM AS
NOK 166,000 rev. · NOK 49,000 profit

ALKA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ALKA EIENDOM AS own?

ALKA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALKA EIENDOM AS

Who owns ALKA EIENDOM AS?

KJELL ARNE BJØRNERUD is the largest registered owner, with 50.0%.

What is the revenue of ALKA EIENDOM AS?

ALKA EIENDOM AS had revenue of NOK 166,000 in 2025.

Who is the general manager of ALKA EIENDOM AS?

Alexander Hagen is registered as general manager of ALKA EIENDOM AS.

Where is ALKA EIENDOM AS based?

ALKA EIENDOM AS has its business address in Vestby.

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.