BIZTRAC BETA
Combined facilities support activities

ROGER OLSEN VEDLIKEHOLD AS

Org. no. 987714816 Limited company (AS) Nes Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 13.6m
Operating profit NOK 2.2m
Equity NOK 4.2m
Incorporated 2005
Employees 14
Share capital NOK 200,000

ROGER OLSEN VEDLIKEHOLD AS is registered as a limited company in Nes, Akershus with organisation number 987714816. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2005 and has 14 registered employees. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Vaktmestertjenester, utomhusarbeider, snørydding og ellers alt som er beslektet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.6m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 13.6m
Operating profit
NOK 2.2m
Equity
NOK 4.2m
Est. value
NOK 9.7m

Financial health · 2024

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.0%
Good
Equity as a share of total capital

Who owns ROGER OLSEN VEDLIKEHOLD AS?

ROGER OLSEN
ROGER OLSEN VEDLIKEHOLD AS
NOK 13.6m rev. · NOK 2.2m profit

ROGER OLSEN VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROGER OLSEN VEDLIKEHOLD AS

Who owns ROGER OLSEN VEDLIKEHOLD AS?

ROGER OLSEN is the largest registered owner, with 100.0%.

What is the revenue of ROGER OLSEN VEDLIKEHOLD AS?

ROGER OLSEN VEDLIKEHOLD AS had revenue of NOK 13.6m in 2024.

Who is the general manager of ROGER OLSEN VEDLIKEHOLD AS?

Roger Olsen is registered as general manager of ROGER OLSEN VEDLIKEHOLD AS.

Where is ROGER OLSEN VEDLIKEHOLD AS based?

ROGER OLSEN VEDLIKEHOLD AS has its business address in Auli.

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.