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

VØN AS

Org. no. 931717154 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −482,000
Equity NOK 73.3m
Incorporated 2023
Share capital NOK 30,000

Signals

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

VØN AS is registered as a limited company in Bærum, Akershus with organisation number 931717154. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere og forvalte investeringer samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −482,000
▼ −135 %
Equity
NOK 73.3m
▲ +6 %
Est. value
NOK 69.7m

Financial health · 2025

Liquidity
175.81
Very good
Current assets ÷ current liabilities
Profitability
7.3%
Satisfactory
Return on total assets
Solidity
99.4%
Very good
Equity as a share of total capital

Who owns VØN AS?

VØN AS
· NOK −482,000 profit

VØN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VØN AS own?

VØN AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about VØN AS

Who owns VØN AS?

VIDAR ØIE NILSEN is the largest registered owner, with 100.0%.

Where is VØN AS based?

VØN AS has its business address in Snarøya.

Property

Business address Teistveien 18, 1367 Snarøya
Cadastral unit 3201-44/567/0/0
Building Tomannsbolig, vertikal · 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.