BIZTRAC BETA
Site preparation

O. VETRHUS MASKINSTASJON AS

Org. no. 915627773 Limited company (AS) Suldal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 410,000
Equity NOK 1.5m
Incorporated 2015
Share capital NOK 100,000

O. VETRHUS MASKINSTASJON AS is registered as a limited company in Suldal, Rogaland with organisation number 915627773. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive maskinstasjon og entreprenørvirksomhet, utleie av maskiner og utstyr, og naturlig tilhørende virksomhet, herunder investering i annen virksomhet og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 410,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 410,000
Equity
NOK 1.5m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns O. VETRHUS MASKINSTASJON AS?

OLAV VETRHUS
O. VETRHUS MASKINSTASJON AS
NOK 2.3m rev. · NOK 410,000 profit

O. VETRHUS MASKINSTASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about O. VETRHUS MASKINSTASJON AS

Who owns O. VETRHUS MASKINSTASJON AS?

OLAV VETRHUS is the largest registered owner, with 100.0%.

What is the revenue of O. VETRHUS MASKINSTASJON AS?

O. VETRHUS MASKINSTASJON AS had revenue of NOK 2.3m in 2024.

Who is the general manager of O. VETRHUS MASKINSTASJON AS?

Olav Vetrhus is registered as general manager of O. VETRHUS MASKINSTASJON AS.

Where is O. VETRHUS MASKINSTASJON AS based?

O. VETRHUS MASKINSTASJON AS has its business address in Suldalsosen.

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.