BIZTRAC BETA
Rental and operating of own or leased real estate

NESSEBY EIENDOM AS

Org. no. 817201032 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 636,000
Equity NOK −3.1m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,1 mill kr).

NESSEBY EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 817201032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eiendom, aksjekjøp og salg”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 636,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 636,000
Equity
NOK −3.1m
Est. value
NOK 3.8m

Financial health · 2024

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

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

Who owns NESSEBY EIENDOM AS?

TANATORGET EIENDOM AS
NESSEBY EIENDOM AS
NOK 1.0m rev. · NOK 636,000 profit

NESSEBY EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NESSEBY EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about NESSEBY EIENDOM AS

Who owns NESSEBY EIENDOM AS?

TANATORGET EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of NESSEBY EIENDOM AS?

NESSEBY EIENDOM AS had revenue of NOK 1.0m in 2024.

Where is NESSEBY EIENDOM AS based?

NESSEBY EIENDOM AS has its business address in Haugesund.

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.