BIZTRAC BETA
Construction of residential and non-residential buildings

RUD OLSEN KONSULT AS

Org. no. 920056539 Limited company (AS) Eidsvoll Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 9.3m
Operating profit NOK 265,000
Equity NOK 103,000
Incorporated 2017
Share capital NOK 30,000

RUD OLSEN KONSULT AS is registered as a limited company in Eidsvoll, Akershus with organisation number 920056539. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg, rådgivning og montering av gasspeiser i tillegg til tømrervirksomhet, eiendomsservice samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.3m in revenue and NOK 265,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.3m
Operating profit
NOK 265,000
Equity
NOK 103,000
Est. value
NOK 927,000

Financial health · 2024

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.7%
Weak
Equity as a share of total capital

Who owns RUD OLSEN KONSULT AS?

MRO HOLDING AS
RUD OLSEN KONSULT AS
NOK 9.3m rev. · NOK 265,000 profit

RUD OLSEN KONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUD OLSEN KONSULT AS

Who owns RUD OLSEN KONSULT AS?

MRO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RUD OLSEN KONSULT AS?

RUD OLSEN KONSULT AS had revenue of NOK 9.3m in 2024.

Who is the general manager of RUD OLSEN KONSULT AS?

Erik Rud Olsen is registered as general manager of RUD OLSEN KONSULT AS.

Where is RUD OLSEN KONSULT AS based?

RUD OLSEN KONSULT AS has its business address in Dal.

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.