BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

HOVE MASKININVEST AS

Org. no. 918708111 Limited company (AS) Sunnfjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 396,000
Operating profit NOK 121,000
Equity NOK 499,000
Incorporated 2017
Share capital NOK 430,000

HOVE MASKININVEST AS is registered as a limited company in Sunnfjord, Vestland with organisation number 918708111. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2017. Registered share capital is NOK 430,000, divided into 430 shares. The company's stated purpose is: “Kjøp, salg, og utleige av maskiner og utstyr til anleggsbransjen. Drive entrepenørvirksomhet, og annet som naturlig faller sammen med dette. Delta i andre selskap ved kjøp av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 396,000 in revenue and NOK 121,000 in operating profit.

Key figures · 2025

Revenue
NOK 396,000
Operating profit
NOK 121,000
Equity
NOK 499,000
Est. value
NOK 640,000

Financial health · 2025

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

Who owns HOVE MASKININVEST AS?

SIR JOHN BEDWARE COMPANY AS
HOVE MASKININVEST AS
NOK 396,000 rev. · NOK 121,000 profit

HOVE MASKININVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOVE MASKININVEST AS

Who owns HOVE MASKININVEST AS?

SIR JOHN BEDWARE COMPANY AS is the largest registered owner, with 100.0%.

What is the revenue of HOVE MASKININVEST AS?

HOVE MASKININVEST AS had revenue of NOK 396,000 in 2025.

Where is HOVE MASKININVEST AS based?

HOVE MASKININVEST AS has its business address in Bygstad.

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.