biztrac. BETA
COMPANY REGISTER PROFILE
923836462 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KAPELLVEIEN 17 AS

Org. no. 923836462 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 662,000
Equity NOK 611,000
Incorporated 2019
Share capital NOK 30,000

KAPELLVEIEN 17 AS is registered as a limited company in Oslo, Oslo with organisation number 923836462. 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 30,000, divided into 300 shares. The company's stated purpose is: “Eie og leie ut eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 662,000 in operating profit.

Former names: DOGGER 1 AS

Key figures · 2025

Revenue
NOK 1.1m
▲ +6 %
Operating profit
NOK 662,000
▼ −13 %
Equity
NOK 611,000
▼ −2 %
Est. value
NOK 928,000

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
6.2%
Satisfactory
Return on total assets
Solidity
5.7%
Weak
Equity as a share of total capital

Who owns KAPELLVEIEN 17 AS?

KAPELLVEIEN 17 AS
NOK 1.1m rev. · NOK 662,000 profit

KAPELLVEIEN 17 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAPELLVEIEN 17 AS

Who owns KAPELLVEIEN 17 AS?

OSLO HANDELSEIENDOMMER AS is the largest registered owner, with 100.0%.

What is the revenue of KAPELLVEIEN 17 AS?

KAPELLVEIEN 17 AS had revenue of NOK 1.1m in 2025.

Who is the general manager of KAPELLVEIEN 17 AS?

Steffen Tronstad is registered as general manager of KAPELLVEIEN 17 AS.

Where is KAPELLVEIEN 17 AS based?

KAPELLVEIEN 17 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.