biztrac. BETA
COMPANY REGISTER PROFILE
915050131 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of cars and light motor vehicles

KUBIKK NORGE AS

Org. no. 915050131 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK −727,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−727k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

KUBIKK NORGE AS is registered as a limited company in Bergen, Vestland with organisation number 915050131. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Franchisedrift, utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Former names: FOLKS HELSE AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
▼ −6 %
Equity
NOK −727,000
▼ −1 %

Financial health · 2025

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

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

Who owns KUBIKK NORGE AS?

KUBIKK NORGE AS
NOK 0 rev. · NOK −4,000 profit

KUBIKK NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KUBIKK NORGE AS

Who owns KUBIKK NORGE AS?

VEGABRA AS is the largest registered owner, with 100.0%.

What is the revenue of KUBIKK NORGE AS?

KUBIKK NORGE AS had revenue of NOK 0 in 2025.

Where is KUBIKK NORGE AS based?

KUBIKK NORGE AS has its business address in Laksevåg.

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.