BIZTRAC BETA
Quarrying of ornamental stone, limestone, gypsum, slate and other stone

OLAV INGSTADSVEI 5 AS

Org. no. 989566903 Limited company (AS) Bærum Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 10.5m
Operating profit NOK 4.6m
Equity NOK 7.3m
Incorporated 2006
Share capital NOK 2.3m

OLAV INGSTADSVEI 5 AS is registered as a limited company in Bærum, Akershus with organisation number 989566903. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 2006. Registered share capital is NOK 2.3m, divided into 100 shares. The company's stated purpose is: “Å eie og drive utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.5m in revenue and NOK 4.6m in operating profit.

Key figures · 2024

Revenue
NOK 10.5m
Operating profit
NOK 4.6m
Equity
NOK 7.3m
Est. value
NOK 14.7m

Financial health · 2024

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

Who owns OLAV INGSTADSVEI 5 AS?

FRANZEFOSS MINERALS AS
OLAV INGSTADSVEI 5 AS
NOK 10.5m rev. · NOK 4.6m profit

OLAV INGSTADSVEI 5 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OLAV INGSTADSVEI 5 AS er morselskap for 4 datterselskaper:

Frequently asked questions about OLAV INGSTADSVEI 5 AS

Who owns OLAV INGSTADSVEI 5 AS?

FRANZEFOSS MINERALS AS is the largest registered owner, with 100.0%.

What is the revenue of OLAV INGSTADSVEI 5 AS?

OLAV INGSTADSVEI 5 AS had revenue of NOK 10.5m in 2024.

Who is the general manager of OLAV INGSTADSVEI 5 AS?

Øystein Roger Ulsletten is registered as general manager of OLAV INGSTADSVEI 5 AS.

Where is OLAV INGSTADSVEI 5 AS based?

OLAV INGSTADSVEI 5 AS has its business address in Rud.

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.