BIZTRAC BETA
Development of building projects

OLERUD EIENDOM AS

Org. no. 923649786 Limited company (AS) Lunner Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 646,000
Operating profit NOK 459,000
Equity NOK 1.9m
Incorporated 2019
Share capital NOK 40,000

OLERUD EIENDOM AS is registered as a limited company in Lunner, Akershus with organisation number 923649786. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Kjøp, utvikling, leie, utleie og/eller salg av fast eiendom og aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 646,000 in revenue and NOK 459,000 in operating profit.

Key figures · 2024

Revenue
NOK 646,000
Operating profit
NOK 459,000
Equity
NOK 1.9m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns OLERUD EIENDOM AS?

OLERUD MALE & SNEKKERVERKSTED AS
OLERUD EIENDOM AS
NOK 646,000 rev. · NOK 459,000 profit

OLERUD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OLERUD EIENDOM AS own?

OLERUD EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OLERUD EIENDOM AS

Who owns OLERUD EIENDOM AS?

OLERUD MALE & SNEKKERVERKSTED AS is the largest registered owner, with 50.0%.

What is the revenue of OLERUD EIENDOM AS?

OLERUD EIENDOM AS had revenue of NOK 646,000 in 2024.

Who is the general manager of OLERUD EIENDOM AS?

Arne Ivar Olerud is registered as general manager of OLERUD EIENDOM AS.

Where is OLERUD EIENDOM AS based?

OLERUD EIENDOM AS has its business address in Lunner.

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.