BIZTRAC BETA
Site preparation

LØVAAS MASKIN AS

Org. no. 925264342 Limited company (AS) Bergen Incorporated 1978 Active
Ownership graph ↗
Revenue 2024 NOK 255.3m
Operating profit NOK 547,000
Equity NOK 50.9m
Incorporated 1978
Employees 94
Share capital NOK 1.0m

LØVAAS MASKIN AS is registered as a limited company in Bergen, Vestland with organisation number 925264342. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1978 and has 94 registered employees. Registered share capital is NOK 1.0m, divided into 500 shares. The company's stated purpose is: “Utføre oppdrag innen maskindrift og transport, kjøp og utleie av utstyr og maskiner og all virksomhet som er forbundet hermed, herunder å delta i andre selskaper med tilsvarende eller beslektet virksomhet gjennom aksje- eller andelseiere. ”. The most recent filed accounts, for the 2024 financial year, show NOK 255.3m in revenue and NOK 547,000 in operating profit.

Key figures · 2024

Revenue
NOK 255.3m
Operating profit
NOK 547,000
Equity
NOK 50.9m
Est. value
NOK 23.8m

Financial health · 2024

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

Who owns LØVAAS MASKIN AS?

E. LØVAAS HOLDING AS
LØVAAS MASKIN AS
NOK 255.3m rev. · NOK 547,000 profit

LØVAAS MASKIN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØVAAS MASKIN AS

Who owns LØVAAS MASKIN AS?

E. LØVAAS HOLDING AS is the largest registered owner, with 55.0%.

What is the revenue of LØVAAS MASKIN AS?

LØVAAS MASKIN AS had revenue of NOK 255.3m in 2024.

Who is the general manager of LØVAAS MASKIN AS?

Eirik Løvaas is registered as general manager of LØVAAS MASKIN AS.

Where is LØVAAS MASKIN AS based?

LØVAAS MASKIN AS has its business address in Blomsterdalen.

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.