BIZTRAC BETA
Site preparation

MASKINENTREPRENØR INGAR LØVER AS

Org. no. 918693408 Limited company (AS) Larvik Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK 2.0m
Equity NOK 7.5m
Incorporated 2017
Share capital NOK 30,000

MASKINENTREPRENØR INGAR LØVER AS is registered as a limited company in Larvik, Vestfold with organisation number 918693408. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Grave- og entreprenørvirksomhet og alt som naturlig hører inn under dette, også deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
Operating profit
NOK 2.0m
Equity
NOK 7.5m
Est. value
NOK 9.8m

Financial health · 2024

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

Who owns MASKINENTREPRENØR INGAR LØVER AS?

INGAR LØVER
MASKINENTREPRENØR INGAR LØVER AS
NOK 6.5m rev. · NOK 2.0m profit

MASKINENTREPRENØR INGAR LØVER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MASKINENTREPRENØR INGAR LØVER AS

Who owns MASKINENTREPRENØR INGAR LØVER AS?

INGAR LØVER is the largest registered owner, with 100.0%.

What is the revenue of MASKINENTREPRENØR INGAR LØVER AS?

MASKINENTREPRENØR INGAR LØVER AS had revenue of NOK 6.5m in 2025.

Who is the general manager of MASKINENTREPRENØR INGAR LØVER AS?

Ingar Løver is registered as general manager of MASKINENTREPRENØR INGAR LØVER AS.

Where is MASKINENTREPRENØR INGAR LØVER AS based?

MASKINENTREPRENØR INGAR LØVER AS has its business address in Steinsholt.

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.