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

CURRENT VALUE HOLDING AS

Org. no. 936710670 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Equity NOK 3.0m
Incorporated 2025
Share capital NOK 201,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-20.

CURRENT VALUE HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 936710670. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 201,000, divided into 182353 shares. The company's stated purpose is: “Hovedkontortjenester, samt erverve, eie og forvalte aksjer og andeler i andre selskaper og alt som naturlig hører inn under dette.”.

Key figures · 2025

Equity
NOK 3.0m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns CURRENT VALUE HOLDING AS?

CURRENT VALUE HOLDING AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about CURRENT VALUE HOLDING AS

Who owns CURRENT VALUE HOLDING AS?

EX LIBRIS AS is the largest registered owner, with 32.9%.

Where is CURRENT VALUE HOLDING AS based?

CURRENT VALUE HOLDING AS has its business address in Bergen.

Property

Business address Kong Oscars gate 68, 5017 Bergen
Cadastral unit 4601-166/550/0/0
Building Annen kontorbygning · 2 units

3 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.