BIZTRAC BETA
Rental and operating of own or leased real estate

LYSEPARKEN HOLDING AS

Org. no. 926626280 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −57,000
Equity NOK 74,000
Incorporated 2021
Share capital NOK 90,000

Signals

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

LYSEPARKEN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 926626280. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 90,000, divided into 300 shares. The company's stated purpose is: “Eie, forvalte og utvikle selskaper, aksjer og eiendommer, og alt som hører innunder dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −57,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −57,000
Equity
NOK 74,000
Est. value
NOK 68,000

Financial health · 2024

Liquidity
4.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
84.4%
Weak
Equity as a share of total capital

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

Who owns LYSEPARKEN HOLDING AS?

SINDRE KNUTSEN
LYSEPARKEN HOLDING AS
NOK 0 rev. · NOK −57,000 profit

LYSEPARKEN HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Group structure

LYSEPARKEN HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about LYSEPARKEN HOLDING AS

Who owns LYSEPARKEN HOLDING AS?

SINDRE KNUTSEN is the largest registered owner, with 33.3%.

What is the revenue of LYSEPARKEN HOLDING AS?

LYSEPARKEN HOLDING AS had revenue of NOK 0 in 2024.

Where is LYSEPARKEN HOLDING AS based?

LYSEPARKEN HOLDING AS has its business address in Blomsterdalen.

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.