BIZTRAC BETA
Rental and operating of own or leased real estate

EDAB EIENDOM AS

Org. no. 994620371 Limited company (AS) Kongsvinger Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 605,000
Operating profit NOK 231,000
Equity NOK 3.7m
Incorporated 2009
Share capital NOK 1.0m

EDAB EIENDOM AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 994620371. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Forretningsmessige virksomheter i forbindelse med utvikling, bygging og utleie av eiendom med tilhørende aktiviteter. Selskapet kan eie eller på annen måte engasjere seg i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 605,000 in revenue and NOK 231,000 in operating profit.

Key figures · 2024

Revenue
NOK 605,000
Operating profit
NOK 231,000
Equity
NOK 3.7m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns EDAB EIENDOM AS?

INGENIØR BJØRN ROTHEIM AS
EDAB EIENDOM AS
NOK 605,000 rev. · NOK 231,000 profit

EDAB EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EDAB EIENDOM AS own?

EDAB EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EDAB EIENDOM AS

Who owns EDAB EIENDOM AS?

INGENIØR BJØRN ROTHEIM AS is the largest registered owner, with 100.0%.

What is the revenue of EDAB EIENDOM AS?

EDAB EIENDOM AS had revenue of NOK 605,000 in 2024.

Where is EDAB EIENDOM AS based?

EDAB EIENDOM AS has its business address in Kongsvinger.

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.