BIZTRAC BETA
Rental and operating of own or leased real estate

DYRSKUEVEIEN 15 AS

Org. no. 992012137 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 18.0m
Operating profit NOK 11.7m
Equity NOK 124.7m
Incorporated 2007
Share capital NOK 330,000

Signals

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

DYRSKUEVEIEN 15 AS is registered as a limited company in Oslo, Oslo with organisation number 992012137. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 330,000, divided into 30000 shares. The company's stated purpose is: “Å eie og/eller drive fast eiendom og investere i andre selskaper, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.0m in revenue and NOK 11.7m in operating profit.

Key figures · 2024

Revenue
NOK 18.0m
Operating profit
NOK 11.7m
Equity
NOK 124.7m
Est. value
NOK 115.8m

Financial health · 2024

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

Who owns DYRSKUEVEIEN 15 AS?

PEF HOLDING AS
DYRSKUEVEIEN 15 AS
NOK 18.0m rev. · NOK 11.7m profit

DYRSKUEVEIEN 15 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DYRSKUEVEIEN 15 AS er morselskap for 42 datterselskaper:

Frequently asked questions about DYRSKUEVEIEN 15 AS

Who owns DYRSKUEVEIEN 15 AS?

PEF HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DYRSKUEVEIEN 15 AS?

DYRSKUEVEIEN 15 AS had revenue of NOK 18.0m in 2024.

Where is DYRSKUEVEIEN 15 AS based?

DYRSKUEVEIEN 15 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.