BIZTRAC BETA
Rental and operating of own or leased real estate

KVELDROVEIEN 19 AS

Org. no. 989551868 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 22.4m
Operating profit NOK 15.3m
Equity NOK 151.3m
Incorporated 2006
Share capital NOK 12.2m

Signals

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

KVELDROVEIEN 19 AS is registered as a limited company in Oslo, Oslo with organisation number 989551868. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 12.2m, divided into 122000 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 22.4m in revenue and NOK 15.3m in operating profit.

Key figures · 2024

Revenue
NOK 22.4m
Operating profit
NOK 15.3m
Equity
NOK 151.3m
Est. value
NOK 141.9m

Financial health · 2024

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

Who owns KVELDROVEIEN 19 AS?

PEF HOLDING AS
KVELDROVEIEN 19 AS
NOK 22.4m rev. · NOK 15.3m profit

KVELDROVEIEN 19 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KVELDROVEIEN 19 AS er morselskap for 42 datterselskaper:

Frequently asked questions about KVELDROVEIEN 19 AS

Who owns KVELDROVEIEN 19 AS?

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

What is the revenue of KVELDROVEIEN 19 AS?

KVELDROVEIEN 19 AS had revenue of NOK 22.4m in 2024.

Where is KVELDROVEIEN 19 AS based?

KVELDROVEIEN 19 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.