BIZTRAC BETA
Rental and operating of own or leased real estate

MICHELETVEIEN 59-61 AS

Org. no. 916037775 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 25.7m
Operating profit NOK 19.4m
Equity NOK 24.1m
Incorporated 2015
Share capital NOK 10.5m

MICHELETVEIEN 59-61 AS is registered as a limited company in Oslo, Oslo with organisation number 916037775. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 10.5m, divided into 10530000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, eie og leie ut fast eiendom; samt alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.7m in revenue and NOK 19.4m in operating profit.

Key figures · 2024

Revenue
NOK 25.7m
Operating profit
NOK 19.4m
Equity
NOK 24.1m
Est. value
NOK 54.4m

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.5%
Good
Equity as a share of total capital

Who owns MICHELETVEIEN 59-61 AS?

EIENDOMSSPAR AS
MICHELETVEIEN 59-61 AS
NOK 25.7m rev. · NOK 19.4m profit

MICHELETVEIEN 59-61 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MICHELETVEIEN 59-61 AS

Who owns MICHELETVEIEN 59-61 AS?

EIENDOMSSPAR AS is the largest registered owner, with 100.0%.

What is the revenue of MICHELETVEIEN 59-61 AS?

MICHELETVEIEN 59-61 AS had revenue of NOK 25.7m in 2024.

Who is the general manager of MICHELETVEIEN 59-61 AS?

Børre Vegard Skjolden is registered as general manager of MICHELETVEIEN 59-61 AS.

Where is MICHELETVEIEN 59-61 AS based?

MICHELETVEIEN 59-61 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.