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

VIULS AS

Org. no. 993397172 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −90,000
Incorporated 2008
Share capital NOK 100,000

Signals

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

VIULS AS is registered as a limited company in Bærum, Akershus with organisation number 993397172. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Inneha eierinteresser i andre selskap, verdipapirhandel, varehandel samt tjenesteytende virksomhet.”.

Key figures · 2025

Operating profit
NOK −90,000
▼ −549 %

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
1.8%
Weak
Return on total assets
Solidity
Not available
Equity as a share of total capital

Who owns VIULS AS?

VIULS AS
· NOK −90,000 profit

VIULS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIULS AS

Who owns VIULS AS?

JARLE VIULS is the largest registered owner, with 100.0%.

Who is the general manager of VIULS AS?

Jarle Viuls is registered as general manager of VIULS AS.

Where is VIULS AS based?

VIULS AS has its business address in Fornebu.

Property

Business address Rolfsbuktalléen 25, 1364 Fornebu
Cadastral unit 3201-41/832/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 18 units

3 companies are registered at this address.

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.