BIZTRAC BETA
COMPANY REGISTER PROFILE
928665178 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

KORABEL AS

Org. no. 928665178 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −33
Equity NOK 645,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−33 kr).

KORABEL AS is registered as a limited company in Oslo, Oslo with organisation number 928665178. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 6 shares. The company's stated purpose is: “Investering i verdipapirer.”.

Key figures · 2025

Operating profit
NOK −33
▲ +0 %
Equity
NOK 645,000
▼ −0 %
Est. value
NOK 758,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
71.9%
Very good
Equity as a share of total capital

Who owns KORABEL AS?

KORABEL AS has 6 registered shareholders:

All shareholders and roles →

Which companies does KORABEL AS own?

KORABEL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KORABEL AS

Who owns KORABEL AS?

TERJE INGE VALDERHAUG is the largest registered owner, with 16.7%.

Where is KORABEL AS based?

KORABEL AS has its business address in Oslo.

Property

Business address Dronning Eufemias gate 16, 0191 Oslo
Cadastral unit 301-234/83/0/0
Building Kontor- og administrasjonsbygning, rådhus · 3 units

891 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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