BIZTRAC BETA
Buying and selling of own real estate

NESHEIM AS

Org. no. 923071547 Limited company (AS) Averøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 8,000
Operating profit NOK −26,000
Equity NOK 936,000
Incorporated 2019
Share capital NOK 130,000

Signals

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

NESHEIM AS is registered as a limited company in Averøy, Møre og Romsdal with organisation number 923071547. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 130,000, divided into 1300 shares. The company's stated purpose is: “Investeringer i næringsvirksomhet, herunder aksjer og andeler, kjøp, salg og utleie av eiendommer og bygninger, båter og lignende, konsulentvirksomhet og det som måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 8,000
Operating profit
NOK −26,000
Equity
NOK 936,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns NESHEIM AS?

RAGNAR OLAV NYSTØYL
NESHEIM AS
NOK 8,000 rev. · NOK −26,000 profit

NESHEIM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NESHEIM AS own?

NESHEIM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NESHEIM AS

Who owns NESHEIM AS?

RAGNAR OLAV NYSTØYL is the largest registered owner, with 50.0%.

What is the revenue of NESHEIM AS?

NESHEIM AS had revenue of NOK 8,000 in 2024.

Where is NESHEIM AS based?

NESHEIM AS has its business address in Averøy.

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.