BIZTRAC BETA
Other real estate activities on a fee or contract basis

NERMO AS

Org. no. 988392057 Limited company (AS) Øyer Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 14.1m
Operating profit NOK 2.4m
Equity NOK 10.8m
Incorporated 2005
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NERMO AS is registered as a limited company in Øyer, Innlandet with organisation number 988392057. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Forvaltning, utvikling og utleie av fast eiendom. Selskapet driver videre utleie av maskiner. Selskapet kan eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.1m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 14.1m
Operating profit
NOK 2.4m
Equity
NOK 10.8m
Est. value
NOK 10.8m

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.3%
Good
Equity as a share of total capital

Who owns NERMO AS?

JOHANNES NERMO
NERMO AS
NOK 14.1m rev. · NOK 2.4m profit

NERMO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NERMO AS own?

NERMO AS holds stakes in 8 companies:

See the full ownership structure →

Group structure

NERMO AS er morselskap for 4 datterselskaper:

Frequently asked questions about NERMO AS

Who owns NERMO AS?

JOHANNES NERMO is the largest registered owner, with 100.0%.

What is the revenue of NERMO AS?

NERMO AS had revenue of NOK 14.1m in 2024.

Where is NERMO AS based?

NERMO 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.