biztrac. BETA
COMPANY REGISTER PROFILE
928135667 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

VILLAVEIEN 3 AS

Org. no. 928135667 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −34,000
Equity NOK −254,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−254k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−34k kr).

VILLAVEIEN 3 AS is registered as a limited company in Oslo, Oslo with organisation number 928135667. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av eiendom, samt andre aktiviteter som er naturlig i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −34,000
▲ +26 %
Equity
NOK −254,000
▼ −15 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-1.4%
Not satisfactory
Return on total assets
Solidity
-10.1%
Weak
Equity as a share of total capital

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

Who owns VILLAVEIEN 3 AS?

VILLAVEIEN 3 AS
NOK 0 rev. · NOK −34,000 profit

VILLAVEIEN 3 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VILLAVEIEN 3 AS

Who owns VILLAVEIEN 3 AS?

VESSØY INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of VILLAVEIEN 3 AS?

VILLAVEIEN 3 AS had revenue of NOK 0 in 2025.

Where is VILLAVEIEN 3 AS based?

VILLAVEIEN 3 AS has its business address in Oslo.

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.