BIZTRAC BETA
Joinery installation

VIL BYGG AS

Org. no. 933025594 Limited company (AS) Askøy Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK −9,000
Equity NOK 13,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

VIL BYGG AS is registered as a limited company in Askøy, Vestland with organisation number 933025594. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Innen bygg og anlegg og andre tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK −9,000
Equity
NOK 13,000
Est. value
NOK 760,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VIL BYGG AS?

VYTENIS LUCINSKAS
VIL BYGG AS
NOK 2.2m rev. · NOK −9,000 profit

VIL BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIL BYGG AS

Who owns VIL BYGG AS?

VYTENIS LUCINSKAS is the largest registered owner, with 100.0%.

What is the revenue of VIL BYGG AS?

VIL BYGG AS had revenue of NOK 2.2m in 2024.

Who is the general manager of VIL BYGG AS?

Vytenis Lucinskas is registered as general manager of VIL BYGG AS.

Where is VIL BYGG AS based?

VIL BYGG AS has its business address in Ask.

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.