BIZTRAC BETA
Restaurant activities

LBL NO SVG AS

Org. no. 921825617 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 11.8m
Operating profit NOK 83,000
Equity NOK 3.3m
Incorporated 2018
Employees 11
Share capital NOK 2.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LBL NO SVG AS is registered as a limited company in Stavanger, Rogaland with organisation number 921825617. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 11 registered employees. Registered share capital is NOK 2.0m, divided into 2000000 shares. The company's stated purpose is: “Drive virksomhet innenfor restaurantdrift og utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.8m in revenue and NOK 83,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.8m
Operating profit
NOK 83,000
Equity
NOK 3.3m
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
63.3%
Very good
Equity as a share of total capital

Who owns LBL NO SVG AS?

LERVIG AS
LBL NO SVG AS
NOK 11.8m rev. · NOK 83,000 profit

LBL NO SVG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LBL NO SVG AS er morselskap for 2 datterselskaper:

Frequently asked questions about LBL NO SVG AS

Who owns LBL NO SVG AS?

LERVIG AS is the largest registered owner, with 100.0%.

What is the revenue of LBL NO SVG AS?

LBL NO SVG AS had revenue of NOK 11.8m in 2024.

Who is the general manager of LBL NO SVG AS?

Anders Heide Kleinstrup is registered as general manager of LBL NO SVG AS.

Where is LBL NO SVG AS based?

LBL NO SVG 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.