BIZTRAC BETA
Site preparation

NERMO MASKIN AS

Org. no. 914764106 Limited company (AS) Øyer Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK −46,000
Equity NOK −2.6m
Incorporated 2014
Employees 5
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

NERMO MASKIN AS is registered as a limited company in Øyer, Innlandet with organisation number 914764106. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet, herunder alle typer grunnarbeider og gravearbeider.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK −46,000
Equity
NOK −2.6m

Financial health · 2024

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-196.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NERMO MASKIN AS?

NERMO AS
NERMO MASKIN AS
NOK 8.5m rev. · NOK −46,000 profit

NERMO MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NERMO MASKIN AS

Who owns NERMO MASKIN AS?

NERMO AS is the largest registered owner, with 50.0%.

What is the revenue of NERMO MASKIN AS?

NERMO MASKIN AS had revenue of NOK 8.5m in 2024.

Who is the general manager of NERMO MASKIN AS?

Per Johan Nermo is registered as general manager of NERMO MASKIN AS.

Where is NERMO MASKIN AS based?

NERMO MASKIN AS has its business address in Øyer.

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.