biztrac. BETA
COMPANY REGISTER PROFILE
933773655 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Activities of amusement parks and theme parks

LEKELANDET HAUGESUND AS

Org. no. 933773655 Limited company (AS) Time Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −338,000
Equity NOK −347,000
Incorporated 2024
Employees 39
Share capital NOK 30,000

Signals

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

LEKELANDET HAUGESUND AS is registered as a limited company in Time, Rogaland with organisation number 933773655. The business is classified under activities of amusement parks and theme parks (NACE 93.210). The company was incorporated in 2024 and has 39 registered employees. Registered share capital is NOK 30,000, divided into 6020 shares. The company's stated purpose is: “Drift av fornøyelses- og temaparker (Lekeland).”.

Key figures · 2025

Operating profit
NOK −338,000
Equity
NOK −347,000
▼ −1526 %

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
-18.7%
Not satisfactory
Return on total assets
Solidity
-9.7%
Weak
Equity as a share of total capital

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

Who owns LEKELANDET HAUGESUND AS?

LEKELANDET HAUGESUND AS
· NOK −338,000 profit

LEKELANDET HAUGESUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEKELANDET HAUGESUND AS

Who owns LEKELANDET HAUGESUND AS?

TALGØ-INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of LEKELANDET HAUGESUND AS?

Anita Talgø is registered as general manager of LEKELANDET HAUGESUND AS.

Where is LEKELANDET HAUGESUND AS based?

LEKELANDET HAUGESUND AS has its business address in Bryne.

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.