biztrac. BETA
COMPANY REGISTER PROFILE
932229579 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

CAPPES VEI 5 AS

Org. no. 932229579 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 623,000
Operating profit NOK 307,000
Equity NOK −734,000
Incorporated 2023
Share capital NOK 60,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−734k kr).

CAPPES VEI 5 AS is registered as a limited company in Bergen, Vestland with organisation number 932229579. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Utiele av egen eller leid fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 623,000 in revenue and NOK 307,000 in operating profit.

Key figures · 2025

Revenue
NOK 623,000
▲ +129 %
Operating profit
NOK 307,000
▲ +2445 %
Equity
NOK −734,000
▼ −41 %
Est. value
NOK 978,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.2%
Weak
Return on total assets
Solidity
-10.0%
Weak
Equity as a share of total capital

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

Who owns CAPPES VEI 5 AS?

CAPPES VEI 5 AS
NOK 623,000 rev. · NOK 307,000 profit

CAPPES VEI 5 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAPPES VEI 5 AS

Who owns CAPPES VEI 5 AS?

VOLDB HOLDING AS is the largest registered owner, with 75.0%.

What is the revenue of CAPPES VEI 5 AS?

CAPPES VEI 5 AS had revenue of NOK 623,000 in 2025.

Where is CAPPES VEI 5 AS based?

CAPPES VEI 5 AS has its business address in Bergen.

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

Report a problem

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