BIZTRAC BETA
Construction of utility projects for fluids

NERLAND MASKIN AS

Org. no. 942144326 Limited company (AS) Hustadvika Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK −975,000
Equity NOK 1.9m
Incorporated 1986
Employees 11
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−975k kr).

NERLAND MASKIN AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 942144326. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 1986 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 80 shares. The company's stated purpose is: “Entreprenørvirksomhet, samt alt som står i for- bindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK −975,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK −975,000
Equity
NOK 1.9m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns NERLAND MASKIN AS?

FRANK NERLAND
NERLAND MASKIN AS
NOK 10.7m rev. · NOK −975,000 profit

NERLAND MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NERLAND MASKIN AS

Who owns NERLAND MASKIN AS?

FRANK NERLAND is the largest registered owner, with 100.0%.

What is the revenue of NERLAND MASKIN AS?

NERLAND MASKIN AS had revenue of NOK 10.7m in 2024.

Who is the general manager of NERLAND MASKIN AS?

Frank Nerland is registered as general manager of NERLAND MASKIN AS.

Where is NERLAND MASKIN AS based?

NERLAND MASKIN AS has its business address in Vevang.

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.