BIZTRAC BETA
Rental and operating of own or leased real estate

KIRKEGATEN 24-26 AS

Org. no. 884470242 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 20.3m
Operating profit NOK 10.4m
Equity NOK 98.9m
Incorporated 2002
Share capital NOK 1.0m

KIRKEGATEN 24-26 AS is registered as a limited company in Oslo, Oslo with organisation number 884470242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er knyttet til fast eiendom og det som naturlig hører til slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.3m in revenue and NOK 10.4m in operating profit.

Key figures · 2024

Revenue
NOK 20.3m
Operating profit
NOK 10.4m
Equity
NOK 98.9m
Est. value
NOK 85.5m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.8%
Good
Equity as a share of total capital

Who owns KIRKEGATEN 24-26 AS?

CAMPUS KRISTIANIA EIENDOM AS
KIRKEGATEN 24-26 AS
NOK 20.3m rev. · NOK 10.4m profit

KIRKEGATEN 24-26 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KIRKEGATEN 24-26 AS er morselskap for 3 datterselskaper:

Frequently asked questions about KIRKEGATEN 24-26 AS

Who owns KIRKEGATEN 24-26 AS?

CAMPUS KRISTIANIA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KIRKEGATEN 24-26 AS?

KIRKEGATEN 24-26 AS had revenue of NOK 20.3m in 2024.

Who is the general manager of KIRKEGATEN 24-26 AS?

Pål Johan Nakken is registered as general manager of KIRKEGATEN 24-26 AS.

Where is KIRKEGATEN 24-26 AS based?

KIRKEGATEN 24-26 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.