BIZTRAC BETA
Rental and operating of own or leased real estate

NEVAN HOLDING AS

Org. no. 919502991 Limited company (AS) Sarpsborg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 24,000
Operating profit NOK −22,000
Equity NOK 3.6m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).
  • Nylig endring 2026-06-23 Adresseendring registrert 2026-06-23.

NEVAN HOLDING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 919502991. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 24,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 24,000
Operating profit
NOK −22,000
Equity
NOK 3.6m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns NEVAN HOLDING AS?

ØIVIND HAUGSTEN HANSEN
NEVAN HOLDING AS
NOK 24,000 rev. · NOK −22,000 profit

NEVAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NEVAN HOLDING AS own?

NEVAN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NEVAN HOLDING AS

Who owns NEVAN HOLDING AS?

ØIVIND HAUGSTEN HANSEN is the largest registered owner, with 100.0%.

What is the revenue of NEVAN HOLDING AS?

NEVAN HOLDING AS had revenue of NOK 24,000 in 2025.

Where is NEVAN HOLDING AS based?

NEVAN HOLDING AS has its business address in Borgenhaugen.

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.