BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

NICOLAISSEN HOLDING AS

Org. no. 935432049 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 45,000
Incorporated 2025
Share capital NOK 45,000

Signals

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

NICOLAISSEN HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 935432049. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2025. Registered share capital is NOK 45,000, divided into 45000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK 45,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 NICOLAISSEN HOLDING AS?

BJØRN OTTO NICOLAISSEN
NICOLAISSEN HOLDING AS
· NOK −13,000 profit

NICOLAISSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NICOLAISSEN HOLDING AS own?

NICOLAISSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NICOLAISSEN HOLDING AS

Who owns NICOLAISSEN HOLDING AS?

BJØRN OTTO NICOLAISSEN is the largest registered owner, with 100.0%.

Where is NICOLAISSEN HOLDING AS based?

NICOLAISSEN HOLDING AS has its business address in Drammen.

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.