BIZTRAC BETA
Rental and operating of own or leased real estate

AKERSGATA 51 AS

Org. no. 924115181 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 20.3m
Operating profit NOK −17.7m
Equity NOK 359.0m
Incorporated 2019
Share capital NOK 2.4m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17,7 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AKERSGATA 51 AS is registered as a limited company in Oslo, Oslo with organisation number 924115181. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 2.4m, divided into 1 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, samt enhver virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.3m in revenue and NOK −17.7m in operating profit.

Key figures · 2024

Revenue
NOK 20.3m
Operating profit
NOK −17.7m
Equity
NOK 359.0m
Est. value
NOK 327.5m

Financial health · 2024

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

Who owns AKERSGATA 51 AS?

MALLING CORE PLUS II HOLDING AS
AKERSGATA 51 AS
NOK 20.3m rev. · NOK −17.7m profit

AKERSGATA 51 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKERSGATA 51 AS

Who owns AKERSGATA 51 AS?

MALLING CORE PLUS II HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AKERSGATA 51 AS?

AKERSGATA 51 AS had revenue of NOK 20.3m in 2024.

Where is AKERSGATA 51 AS based?

AKERSGATA 51 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.