BIZTRAC BETA
Uoppgitt

ESPEN NICOLAYSEN AS

Org. no. 923004904 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −40,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−40k kr).

ESPEN NICOLAYSEN AS is registered as a limited company in Asker, Akershus with organisation number 923004904. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −40,000

Financial health · 2025

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

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

Who owns ESPEN NICOLAYSEN AS?

ESPEN NICOLAYSEN
ESPEN NICOLAYSEN AS
NOK 0 rev. · NOK 0 profit

ESPEN NICOLAYSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESPEN NICOLAYSEN AS own?

ESPEN NICOLAYSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESPEN NICOLAYSEN AS

Who owns ESPEN NICOLAYSEN AS?

ESPEN NICOLAYSEN is the largest registered owner, with 100.0%.

What is the revenue of ESPEN NICOLAYSEN AS?

ESPEN NICOLAYSEN AS had revenue of NOK 0 in 2025.

Who is the general manager of ESPEN NICOLAYSEN AS?

Espen Nicolaysen is registered as general manager of ESPEN NICOLAYSEN AS.

Where is ESPEN NICOLAYSEN AS based?

ESPEN NICOLAYSEN AS has its business address in Vollen.

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.