BIZTRAC BETA
COMPANY REGISTER PROFILE
936148514 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

NEVSEN HOLDING AS

Org. no. 936148514 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2 kr).

NEVSEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 936148514. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Erverv, planlegging og prosjektering, utbygging, salg, drift og utleie av eiendom og bygg. Videre har selskapet til formål å organisere eller delta i tiltak eller selskap som har sammenheng med ovennevnte formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2
Equity
NOK 23,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns NEVSEN HOLDING AS?

SVEN MYRDAHL OPALIC
NEVSEN HOLDING AS
NOK 0 rev. · NOK −2 profit

NEVSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEVSEN HOLDING AS

Who owns NEVSEN HOLDING AS?

SVEN MYRDAHL OPALIC is the largest registered owner, with 100.0%.

What is the revenue of NEVSEN HOLDING AS?

NEVSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is NEVSEN HOLDING AS based?

NEVSEN HOLDING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.