BIZTRAC BETA
General medical practice activities

VANNKUNSTEN HOLDING AS

Org. no. 933735478 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −400
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−400 kr).
  • Nylig endring 2026-05-20 Adresseendring registrert 2026-05-20.

VANNKUNSTEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 933735478. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å investere og forvalte investeringer som selskaper, aksjer, eiendom og andre eiendeler.”.

Key figures · 2024

Operating profit
NOK −400
Equity
NOK 24,000
Est. value
NOK 37,000

Financial health · 2024

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 VANNKUNSTEN HOLDING AS?

ALEXANDER BRANA ROSIC
VANNKUNSTEN HOLDING AS
· NOK −400 profit

VANNKUNSTEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VANNKUNSTEN HOLDING AS own?

VANNKUNSTEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VANNKUNSTEN HOLDING AS

Who owns VANNKUNSTEN HOLDING AS?

ALEXANDER BRANA ROSIC is the largest registered owner, with 100.0%.

Who is the general manager of VANNKUNSTEN HOLDING AS?

Alexander Brana Rosic is registered as general manager of VANNKUNSTEN HOLDING AS.

Where is VANNKUNSTEN HOLDING AS based?

VANNKUNSTEN 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 15.06.2026.

Report a problem

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