BIZTRAC BETA
Rental and operating of own or leased real estate

ELSAVE EIENDOM II AS

Org. no. 931999761 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 6.0m
Incorporated 2023
Share capital NOK 30,000

ELSAVE EIENDOM II AS is registered as a limited company in Drammen, Buskerud with organisation number 931999761. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investering i aksjer, andre selskapsandeler, øvrige finansielle instrumenter og fast eiendom, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 6.0m
Est. value
NOK 5.5m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns ELSAVE EIENDOM II AS?

ELSAVE EIENDOM AS
ELSAVE EIENDOM II AS
NOK 0 rev. · NOK 0 profit

ELSAVE EIENDOM II AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELSAVE EIENDOM II AS own?

ELSAVE EIENDOM II AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELSAVE EIENDOM II AS

Who owns ELSAVE EIENDOM II AS?

ELSAVE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ELSAVE EIENDOM II AS?

ELSAVE EIENDOM II AS had revenue of NOK 0 in 2025.

Where is ELSAVE EIENDOM II AS based?

ELSAVE EIENDOM II AS has its business address in Drammen.

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.