BIZTRAC BETA
Rental and operating of own or leased real estate

KLP JEKSLEVEIEN 50 AS

Org. no. 926777297 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 11.1m
Operating profit NOK 7.1m
Equity NOK 467,000
Incorporated 2021
Share capital NOK 185,000

Signals

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

KLP JEKSLEVEIEN 50 AS is registered as a limited company in Oslo, Oslo with organisation number 926777297. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 185,000, divided into 184935 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.1m in revenue and NOK 7.1m in operating profit.

Key figures · 2025

Revenue
NOK 11.1m
Operating profit
NOK 7.1m
Equity
NOK 467,000
Est. value
NOK 14.0m

Financial health · 2025

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

Who owns KLP JEKSLEVEIEN 50 AS?

BULK INDUSTRIAL REAL ESTATE AS
KLP JEKSLEVEIEN 50 AS
NOK 11.1m rev. · NOK 7.1m profit

KLP JEKSLEVEIEN 50 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLP JEKSLEVEIEN 50 AS

Who owns KLP JEKSLEVEIEN 50 AS?

BULK INDUSTRIAL REAL ESTATE AS is the largest registered owner, with 100.0%.

What is the revenue of KLP JEKSLEVEIEN 50 AS?

KLP JEKSLEVEIEN 50 AS had revenue of NOK 11.1m in 2025.

Where is KLP JEKSLEVEIEN 50 AS based?

KLP JEKSLEVEIEN 50 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.