biztrac. BETA
COMPANY REGISTER PROFILE
931684485 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

VILJI AS

Org. no. 931684485 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −22
Equity NOK 160,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

VILJI AS is registered as a limited company in Drammen, Buskerud with organisation number 931684485. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22
▼ −1000 %
Equity
NOK 160,000
▲ +555 %
Est. value
NOK 979,000

Financial health · 2025

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
41.0%
Very good
Return on total assets
Solidity
45.6%
Very good
Equity as a share of total capital

Who owns VILJI AS?

VILJI AS
NOK 0 rev. · NOK −22 profit

VILJI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VILJI AS own?

VILJI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VILJI AS

Who owns VILJI AS?

Arny Lara Dadadottir is the largest registered owner, with 100.0%.

What is the revenue of VILJI AS?

VILJI AS had revenue of NOK 0 in 2025.

Who is the general manager of VILJI AS?

Arny Lara Dadadottir is registered as general manager of VILJI AS.

Where is VILJI AS based?

VILJI AS has its business address in Drammen.

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.