BIZTRAC BETA
Rental and operating of own or leased real estate

DRONNING MAUDS GATE 1-3 AS

Org. no. 915607438 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 116.2m
Operating profit NOK 79.5m
Equity NOK 1.1bn
Incorporated 2015
Share capital NOK 4.0m

Signals

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

DRONNING MAUDS GATE 1-3 AS is registered as a limited company in Oslo, Oslo with organisation number 915607438. 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 4.0m, divided into 1000 shares. The company's stated purpose is: “Å eie, drifte og drive utleie av fast eiendom, og alt annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 116.2m in revenue and NOK 79.5m in operating profit.

Key figures · 2024

Revenue
NOK 116.2m
Operating profit
NOK 79.5m
Equity
NOK 1.1bn
Est. value
NOK 972.3m

Financial health · 2024

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

Who owns DRONNING MAUDS GATE 1-3 AS?

DMG 1-3 AS
DRONNING MAUDS GATE 1-3 AS
NOK 116.2m rev. · NOK 79.5m profit

DRONNING MAUDS GATE 1-3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRONNING MAUDS GATE 1-3 AS

Who owns DRONNING MAUDS GATE 1-3 AS?

DMG 1-3 AS is the largest registered owner, with 100.0%.

What is the revenue of DRONNING MAUDS GATE 1-3 AS?

DRONNING MAUDS GATE 1-3 AS had revenue of NOK 116.2m in 2024.

Where is DRONNING MAUDS GATE 1-3 AS based?

DRONNING MAUDS GATE 1-3 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.