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

VONABU AS

Org. no. 934766776 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 3.5m
Incorporated 2024
Share capital NOK 32,000

Signals

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

VONABU AS is registered as a limited company in Bergen, Vestland with organisation number 934766776. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 32,000, divided into 1050 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 3.5m
▲ +5858 %
Est. value
NOK 9.6m

Financial health · 2025

Liquidity
887.48
Very good
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 VONABU AS?

VONABU AS
· NOK −16,000 profit

VONABU AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VONABU AS own?

VONABU AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VONABU AS

Who owns VONABU AS?

SILJA KRISTIANSEN BRULAND is the largest registered owner, with 100.0%.

Where is VONABU AS based?

VONABU AS has its business address in Sandsli.

Property

Business address Gosen 63, 5253 Sandsli
Cadastral unit 4601-37/250/0/0
Building Rekkehus · 1 unit

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.