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

NIMO EIGEDOM AS

Org. no. 813728982 Limited company (AS) Ørsta Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 913,000
Operating profit NOK 668,000
Equity NOK 661,000
Incorporated 2014
Share capital NOK 1.4m

NIMO EIGEDOM AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 813728982. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2014. Registered share capital is NOK 1.4m, divided into 2000 shares. The company's stated purpose is: “Kjøp, sal og forvaltning av eigedom og aksjar, og alt står i samband med dette samt oppgåver som normalt ligg under rolla som holdingselskap. Selskapet kan også yte konsulentvistad til andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 913,000 in revenue and NOK 668,000 in operating profit.

Key figures · 2025

Revenue
NOK 913,000
Operating profit
NOK 668,000
Equity
NOK 661,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns NIMO EIGEDOM AS?

NIMO INVEST AS
NIMO EIGEDOM AS
NOK 913,000 rev. · NOK 668,000 profit

NIMO EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIMO EIGEDOM AS

Who owns NIMO EIGEDOM AS?

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

What is the revenue of NIMO EIGEDOM AS?

NIMO EIGEDOM AS had revenue of NOK 913,000 in 2025.

Who is the general manager of NIMO EIGEDOM AS?

Nikolas Ivar Moe is registered as general manager of NIMO EIGEDOM AS.

Where is NIMO EIGEDOM AS based?

NIMO EIGEDOM AS has its business address in Ørsta.

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.