BIZTRAC BETA
Activities of housing cooperatives

MAJORSTUVEIEN 13 AS

Org. no. 921307020 Limited company (AS) Oslo Incorporated 1957 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 198,000
Equity NOK −770,000
Incorporated 1957
Share capital NOK 101,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−770k kr).

MAJORSTUVEIEN 13 AS is registered as a limited company in Oslo, Oslo with organisation number 921307020. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1957. Registered share capital is NOK 101,000, divided into 738 shares. The company's stated purpose is: “Boligaksjeselskap som har som formål å skaffe aksjeeierne bruksrett (borett) til egen bolig og aksjeeiers bruksrett til kontorlokaler i byggets underetasje.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 198,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 198,000
Equity
NOK −770,000
Est. value
NOK 992,000

Financial health · 2024

Liquidity
10.44
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-43.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MAJORSTUVEIEN 13 AS?

No shareholders are registered for MAJORSTUVEIEN 13 AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does MAJORSTUVEIEN 13 AS own?

MAJORSTUVEIEN 13 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MAJORSTUVEIEN 13 AS

What is the revenue of MAJORSTUVEIEN 13 AS?

MAJORSTUVEIEN 13 AS had revenue of NOK 1.6m in 2024.

Where is MAJORSTUVEIEN 13 AS based?

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