BIZTRAC BETA
Other captive investment companies

EIKA VBB AS

Org. no. 921859708 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 995,000
Operating profit NOK −147,000
Equity NOK 845.2m
Incorporated 2018
Share capital NOK 1.4m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−147k kr).

EIKA VBB AS is registered as a limited company in Oslo, Oslo with organisation number 921859708. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 1.4m, divided into 136043 shares. The company's stated purpose is: “Å eie aksjer i VBB AS samt i ivareta Eika Alliansens interesser i alle forhold vedrørende VBB AS, herunder delta i andre selskaper innenfor VBB AS sitt forretningsområde. Selskapet skal ikke drive annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 995,000 in revenue and NOK −147,000 in operating profit.

Key figures · 2024

Revenue
NOK 995,000
Operating profit
NOK −147,000
Equity
NOK 845.2m
Est. value
NOK 585.2m

Financial health · 2024

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

Who owns EIKA VBB AS?

ROGALAND SPAREBANK
EIKA VBB AS
NOK 995,000 rev. · NOK −147,000 profit

EIKA VBB AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does EIKA VBB AS own?

EIKA VBB AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIKA VBB AS

Who owns EIKA VBB AS?

ROGALAND SPAREBANK is the largest registered owner, with 9.8%.

What is the revenue of EIKA VBB AS?

EIKA VBB AS had revenue of NOK 995,000 in 2024.

Where is EIKA VBB AS based?

EIKA VBB AS has its business address in Oslo.

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

Report a problem

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