BIZTRAC BETA
Other technical consultancy

NESSA HOLDING AS

Org. no. 928111741 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 1.2m
Equity NOK 1.4m
Incorporated 2021
Share capital NOK 30,000

NESSA HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 928111741. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Teknisk konsulent tjenester innen olje og gass, samt investering i noterte og unoterte aksjeselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 1.2m
Equity
NOK 1.4m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns NESSA HOLDING AS?

JOACHIM NESSA
NESSA HOLDING AS
NOK 2.8m rev. · NOK 1.2m profit

NESSA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NESSA HOLDING AS own?

NESSA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

NESSA HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about NESSA HOLDING AS

Who owns NESSA HOLDING AS?

JOACHIM NESSA is the largest registered owner, with 100.0%.

What is the revenue of NESSA HOLDING AS?

NESSA HOLDING AS had revenue of NOK 2.8m in 2025.

Who is the general manager of NESSA HOLDING AS?

Joachim Nessa is registered as general manager of NESSA HOLDING AS.

Where is NESSA HOLDING AS based?

NESSA HOLDING AS has its business address in Stavanger.

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.