BIZTRAC BETA
COMPANY REGISTER PROFILE
989240927 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Buying and selling of own real estate

BJØRN MADSSTUEN EIENDOM AS

Org. no. 989240927 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −817,000
Equity NOK 5.7m
Incorporated 2005
Share capital NOK 100,000

Signals

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

BJØRN MADSSTUEN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 989240927. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investerings og holdingsvirksomhet og alt som står i forbindelse med dette”.

Key figures · 2024

Operating profit
NOK −817,000
Equity
NOK 5.7m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns BJØRN MADSSTUEN EIENDOM AS?

ULLEVÅLSVEIEN 10 AS
BJØRN MADSSTUEN EIENDOM AS
· NOK −817,000 profit

BJØRN MADSSTUEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BJØRN MADSSTUEN EIENDOM AS own?

BJØRN MADSSTUEN EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BJØRN MADSSTUEN EIENDOM AS

Who owns BJØRN MADSSTUEN EIENDOM AS?

ULLEVÅLSVEIEN 10 AS is the largest registered owner, with 99.0%.

Who is the general manager of BJØRN MADSSTUEN EIENDOM AS?

Bjørn Eivind Madsstuen is registered as general manager of BJØRN MADSSTUEN EIENDOM AS.

Where is BJØRN MADSSTUEN EIENDOM AS based?

BJØRN MADSSTUEN EIENDOM 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.