BIZTRAC BETA
Other recreational activities

FUN CENTER NES AS

Org. no. 931437801 Limited company (AS) Nesbyen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 432,000
Operating profit NOK −553,000
Equity NOK −1.3m
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−553k kr).

FUN CENTER NES AS is registered as a limited company in Nesbyen, Buskerud with organisation number 931437801. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie, drive, kjøpe, selge og utvikle aktivitetssenter og bar og restaurant. Samt investering i selskap som driver med det samme.”. The most recent filed accounts, for the 2024 financial year, show NOK 432,000 in revenue and NOK −553,000 in operating profit.

Key figures · 2024

Revenue
NOK 432,000
Operating profit
NOK −553,000
Equity
NOK −1.3m

Financial health · 2024

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

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

Who owns FUN CENTER NES AS?

VÆKERØ INVEST AS
FUN CENTER NES AS
NOK 432,000 rev. · NOK −553,000 profit

FUN CENTER NES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FUN CENTER NES AS

Who owns FUN CENTER NES AS?

VÆKERØ INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of FUN CENTER NES AS?

FUN CENTER NES AS had revenue of NOK 432,000 in 2024.

Where is FUN CENTER NES AS based?

FUN CENTER NES 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.