BIZTRAC BETA
Site preparation

BRØDRENE MUSLAND MASKIN AS

Org. no. 925384836 Limited company (AS) Kvinnherad Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 67.8m
Operating profit NOK 16.1m
Equity NOK 11.1m
Incorporated 2020
Employees 15
Share capital NOK 500,000

BRØDRENE MUSLAND MASKIN AS is registered as a limited company in Kvinnherad, Vestland with organisation number 925384836. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020 and has 15 registered employees. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet med graving, muring og utleie av maskiner, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 67.8m in revenue and NOK 16.1m in operating profit.

Key figures · 2025

Revenue
NOK 67.8m
Operating profit
NOK 16.1m
Equity
NOK 11.1m
Est. value
NOK 51.2m

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.6%
Good
Equity as a share of total capital

Who owns BRØDRENE MUSLAND MASKIN AS?

MUSLAND HOLDING AS
BRØDRENE MUSLAND MASKIN AS
NOK 67.8m rev. · NOK 16.1m profit

BRØDRENE MUSLAND MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRØDRENE MUSLAND MASKIN AS

Who owns BRØDRENE MUSLAND MASKIN AS?

MUSLAND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRØDRENE MUSLAND MASKIN AS?

BRØDRENE MUSLAND MASKIN AS had revenue of NOK 67.8m in 2025.

Who is the general manager of BRØDRENE MUSLAND MASKIN AS?

Roar Musland is registered as general manager of BRØDRENE MUSLAND MASKIN AS.

Where is BRØDRENE MUSLAND MASKIN AS based?

BRØDRENE MUSLAND MASKIN AS has its business address in Uskedalen.

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.