BIZTRAC BETA
Other real estate activities on a fee or contract basis

STORMBULL EIENDOM SVERIGE AS

Org. no. 919039108 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −61,000
Equity NOK 7.5m
Incorporated 2017
Share capital NOK 45,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−61k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STORMBULL EIENDOM SVERIGE AS is registered as a limited company in Oslo, Oslo with organisation number 919039108. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2017. Registered share capital is NOK 45,000, divided into 150 shares. The company's stated purpose is: “Eie andeler/aksjer i eiendomsprosjekter.”.

Key figures · 2025

Operating profit
NOK −61,000
Equity
NOK 7.5m
Est. value
NOK 26.9m

Financial health · 2025

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

Who owns STORMBULL EIENDOM SVERIGE AS?

STORMBULL EIENDOM AS
STORMBULL EIENDOM SVERIGE AS
· NOK −61,000 profit

STORMBULL EIENDOM SVERIGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STORMBULL EIENDOM SVERIGE AS er morselskap for 6 datterselskaper:

Frequently asked questions about STORMBULL EIENDOM SVERIGE AS

Who owns STORMBULL EIENDOM SVERIGE AS?

STORMBULL EIENDOM AS is the largest registered owner, with 100.0%.

Who is the general manager of STORMBULL EIENDOM SVERIGE AS?

Christian Peder Fossum is registered as general manager of STORMBULL EIENDOM SVERIGE AS.

Where is STORMBULL EIENDOM SVERIGE AS based?

STORMBULL EIENDOM SVERIGE 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.