BIZTRAC BETA
Rental and operating of own or leased real estate

MAJORSTUVEIEN 38 AS

Org. no. 912610187 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 10.8m
Operating profit NOK 6.4m
Equity NOK 16.3m
Incorporated 2013
Share capital NOK 120,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MAJORSTUVEIEN 38 AS is registered as a limited company in Oslo, Oslo with organisation number 912610187. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 120,000, divided into 30 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.8m in revenue and NOK 6.4m in operating profit.

Key figures · 2024

Revenue
NOK 10.8m
Operating profit
NOK 6.4m
Equity
NOK 16.3m
Est. value
NOK 26.1m

Financial health · 2024

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

Who owns MAJORSTUVEIEN 38 AS?

VICTORIA EIENDOM AS
MAJORSTUVEIEN 38 AS
NOK 10.8m rev. · NOK 6.4m profit

MAJORSTUVEIEN 38 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MAJORSTUVEIEN 38 AS er morselskap for 18 datterselskaper:

Frequently asked questions about MAJORSTUVEIEN 38 AS

Who owns MAJORSTUVEIEN 38 AS?

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

What is the revenue of MAJORSTUVEIEN 38 AS?

MAJORSTUVEIEN 38 AS had revenue of NOK 10.8m in 2024.

Where is MAJORSTUVEIEN 38 AS based?

MAJORSTUVEIEN 38 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.