BIZTRAC BETA
Rental and operating of own or leased real estate

OLÅN EIENDOM AS

Org. no. 911740532 Limited company (AS) Time Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 362,000
Operating profit NOK 273,000
Equity NOK 2.4m
Incorporated 2013
Share capital NOK 1.3m

OLÅN EIENDOM AS is registered as a limited company in Time, Rogaland with organisation number 911740532. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 1.3m, divided into 1330 shares. The company's stated purpose is: “Kjøp, salg, utleie av eiendom og salg av andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 362,000 in revenue and NOK 273,000 in operating profit.

Key figures · 2025

Revenue
NOK 362,000
Operating profit
NOK 273,000
Equity
NOK 2.4m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns OLÅN EIENDOM AS?

OLAV ÅNESTAD
OLÅN EIENDOM AS
NOK 362,000 rev. · NOK 273,000 profit

OLÅN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLÅN EIENDOM AS

Who owns OLÅN EIENDOM AS?

OLAV ÅNESTAD is the largest registered owner, with 100.0%.

What is the revenue of OLÅN EIENDOM AS?

OLÅN EIENDOM AS had revenue of NOK 362,000 in 2025.

Who is the general manager of OLÅN EIENDOM AS?

Olav Ånestad is registered as general manager of OLÅN EIENDOM AS.

Where is OLÅN EIENDOM AS based?

OLÅN EIENDOM AS has its business address in Bryne.

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.