BIZTRAC BETA
Restaurant activities

LORELEY AS

Org. no. 932304589 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 954,000
Operating profit NOK −102,000
Equity NOK −125,000
Incorporated 2023
Employees 8
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−125k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−102k kr).

LORELEY AS is registered as a limited company in Stavanger, Rogaland with organisation number 932304589. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal selge varer og tjenester innen restaurantdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 954,000 in revenue and NOK −102,000 in operating profit.

Key figures · 2024

Revenue
NOK 954,000
Operating profit
NOK −102,000
Equity
NOK −125,000

Financial health · 2024

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

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

Who owns LORELEY AS?

NINA SVALESTAD JOHANSEN
LORELEY AS
NOK 954,000 rev. · NOK −102,000 profit

LORELEY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LORELEY AS

Who owns LORELEY AS?

NINA SVALESTAD JOHANSEN is the largest registered owner, with 50.0%.

What is the revenue of LORELEY AS?

LORELEY AS had revenue of NOK 954,000 in 2024.

Who is the general manager of LORELEY AS?

Jonas Lorenz Illing is registered as general manager of LORELEY AS.

Where is LORELEY AS based?

LORELEY AS has its business address in Stavanger.

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.