BIZTRAC BETA
Development of building projects

VOLELISTØLEN AS

Org. no. 932750325 Limited company (AS) Nesbyen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK −48,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

VOLELISTØLEN AS is registered as a limited company in Nesbyen, Buskerud with organisation number 932750325. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling av fast eiendom for salg og utleie. Selskapet kan videre delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK −48,000

Financial health · 2025

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

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

Who owns VOLELISTØLEN AS?

Øyvind Frekeplass
VOLELISTØLEN AS
NOK 0 rev. · NOK −24,000 profit

VOLELISTØLEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOLELISTØLEN AS

Who owns VOLELISTØLEN AS?

Øyvind Frekeplass is the largest registered owner, with 100.0%.

What is the revenue of VOLELISTØLEN AS?

VOLELISTØLEN AS had revenue of NOK 0 in 2025.

Who is the general manager of VOLELISTØLEN AS?

Øyvind Frekeplass is registered as general manager of VOLELISTØLEN AS.

Where is VOLELISTØLEN AS based?

VOLELISTØLEN AS has its business address in Nesbyen.

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.