BIZTRAC BETA
Support services to forestry

MELHUS MASKINDRIFT AS

Org. no. 927003848 Limited company (AS) Lindesnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 20.3m
Operating profit NOK 1.9m
Equity NOK 3.0m
Incorporated 2021
Employees 7
Share capital NOK 280,000

MELHUS MASKINDRIFT AS is registered as a limited company in Lindesnes, Agder with organisation number 927003848. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2021 and has 7 registered employees. Registered share capital is NOK 280,000, divided into 2800 shares. The company's stated purpose is: “Maskindrift og lignende, samt annet som naturlig kan knyttes til dette. Å eie aksjer og andeler i andre selskap, og investering i fast eiendom og annet.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.3m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 20.3m
Operating profit
NOK 1.9m
Equity
NOK 3.0m
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns MELHUS MASKINDRIFT AS?

DANIEL MELHUS INVEST AS
MELHUS MASKINDRIFT AS
NOK 20.3m rev. · NOK 1.9m profit

MELHUS MASKINDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MELHUS MASKINDRIFT AS

Who owns MELHUS MASKINDRIFT AS?

DANIEL MELHUS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of MELHUS MASKINDRIFT AS?

MELHUS MASKINDRIFT AS had revenue of NOK 20.3m in 2024.

Who is the general manager of MELHUS MASKINDRIFT AS?

Daniel Larsen Melhus is registered as general manager of MELHUS MASKINDRIFT AS.

Where is MELHUS MASKINDRIFT AS based?

MELHUS MASKINDRIFT AS has its business address in Lindesnes.

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.