BIZTRAC BETA
Rental and operating of own or leased real estate

NESSET OG EIDEM AS

Org. no. 997280059 Limited company (AS) Ulstein Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −20,000
Equity NOK 365,000
Incorporated 2011
Share capital NOK 400,000

Signals

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

NESSET OG EIDEM AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 997280059. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Kjøp, sal, drift og utleige av fast eigedom, medregna deltaking i andre selskap med liknande føremål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 365,000
Est. value
NOK 333,000

Financial health · 2024

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

Who owns NESSET OG EIDEM AS?

TRYGG INFRA AS
NESSET OG EIDEM AS
NOK 0 rev. · NOK −20,000 profit

NESSET OG EIDEM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESSET OG EIDEM AS

Who owns NESSET OG EIDEM AS?

TRYGG INFRA AS is the largest registered owner, with 100.0%.

What is the revenue of NESSET OG EIDEM AS?

NESSET OG EIDEM AS had revenue of NOK 0 in 2024.

Who is the general manager of NESSET OG EIDEM AS?

Inge Eidem is registered as general manager of NESSET OG EIDEM AS.

Where is NESSET OG EIDEM AS based?

NESSET OG EIDEM AS has its business address in Ulsteinvik.

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.