BIZTRAC BETA
COMPANY REGISTER PROFILE
990632057 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Freight ocean transport

V-BULK AS

Org. no. 990632057 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −71,000
Equity NOK 11.8m
Incorporated 2006
Share capital NOK 2.1m

Signals

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

V-BULK AS is registered as a limited company in Bergen, Vestland with organisation number 990632057. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2006. Registered share capital is NOK 2.1m, divided into 100 shares. The company's stated purpose is: “Komplementar i V-Bulk KS.”.

Key figures · 2025

Operating profit
NOK −71,000
Equity
NOK 11.8m
Est. value
NOK 12.5m

Financial health · 2025

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

Who owns V-BULK AS?

V-BULK AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about V-BULK AS

Who owns V-BULK AS?

SEVEN SEAS SKIPSINVEST AS is the largest registered owner, with 65.0%.

Who is the general manager of V-BULK AS?

Christian Gerhard Sundt is registered as general manager of V-BULK AS.

Where is V-BULK AS based?

V-BULK AS has its business address in Nesttun.

Property

Business address Østre Nesttunvegen 10, 5221 Nesttun
Cadastral unit 4601-42/607/0/0
Building Kjøpesenter, varehus · 1 unit

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