BIZTRAC BETA
Buying and selling of own real estate

STOKKE EIENDOM I AS

Org. no. 866716382 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −212,000
Equity NOK 69.6m
Incorporated 1993
Share capital NOK 280,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−212k kr).

STOKKE EIENDOM I AS is registered as a limited company in Oslo, Oslo with organisation number 866716382. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1993. Registered share capital is NOK 280,000, divided into 100 shares. The company's stated purpose is: “Investeringer i fast eiendom og annet, samt deltakelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −212,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −212,000
Equity
NOK 69.6m
Est. value
NOK 62.7m

Financial health · 2024

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

Who owns STOKKE EIENDOM I AS?

KNUT MARIUS BULL STOKKE
STOKKE EIENDOM I AS
NOK 1.1m rev. · NOK −212,000 profit

STOKKE EIENDOM I AS has 4 registered shareholders:

All shareholders and roles →

Which companies does STOKKE EIENDOM I AS own?

STOKKE EIENDOM I AS holds stakes in 15 companies:

See the full ownership structure →

Frequently asked questions about STOKKE EIENDOM I AS

Who owns STOKKE EIENDOM I AS?

KNUT MARIUS BULL STOKKE is the largest registered owner, with 80.0%.

What is the revenue of STOKKE EIENDOM I AS?

STOKKE EIENDOM I AS had revenue of NOK 1.1m in 2024.

Where is STOKKE EIENDOM I AS based?

STOKKE EIENDOM I 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.