BIZTRAC BETA
Rental and operating of own or leased real estate

KIRKEHAUGSVEIEN 4 AS

Org. no. 918653678 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −26,000
Equity NOK −1.3m
Incorporated 2017
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−26k kr).

KIRKEHAUGSVEIEN 4 AS is registered as a limited company in Oslo, Oslo with organisation number 918653678. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Drive utleie og utvikling av, samt investering i, fast eiendom og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −26,000
Equity
NOK −1.3m

Financial health · 2024

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KIRKEHAUGSVEIEN 4 AS?

JCF AS
KIRKEHAUGSVEIEN 4 AS
NOK 1.1m rev. · NOK −26,000 profit

KIRKEHAUGSVEIEN 4 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIRKEHAUGSVEIEN 4 AS

Who owns KIRKEHAUGSVEIEN 4 AS?

JCF AS is the largest registered owner, with 50.0%.

What is the revenue of KIRKEHAUGSVEIEN 4 AS?

KIRKEHAUGSVEIEN 4 AS had revenue of NOK 1.1m in 2024.

Where is KIRKEHAUGSVEIEN 4 AS based?

KIRKEHAUGSVEIEN 4 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.