BIZTRAC BETA
Restaurant activities

RESTAURANTDRIFT LYNGDAL AS

Org. no. 920359450 Limited company (AS) Lyngdal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 10.4m
Operating profit NOK 335,000
Equity NOK 1.9m
Incorporated 2018
Employees 15
Share capital NOK 210,000

RESTAURANTDRIFT LYNGDAL AS is registered as a limited company in Lyngdal, Agder with organisation number 920359450. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 15 registered employees. Registered share capital is NOK 210,000, divided into 30000 shares. The company's stated purpose is: “Restaurant og cateringvirksomhet samt alt som står i forbindelse med dette, herunder deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.4m in revenue and NOK 335,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.4m
Operating profit
NOK 335,000
Equity
NOK 1.9m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns RESTAURANTDRIFT LYNGDAL AS?

BETH ONES
RESTAURANTDRIFT LYNGDAL AS
NOK 10.4m rev. · NOK 335,000 profit

RESTAURANTDRIFT LYNGDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESTAURANTDRIFT LYNGDAL AS

Who owns RESTAURANTDRIFT LYNGDAL AS?

BETH ONES is the largest registered owner, with 100.0%.

What is the revenue of RESTAURANTDRIFT LYNGDAL AS?

RESTAURANTDRIFT LYNGDAL AS had revenue of NOK 10.4m in 2024.

Who is the general manager of RESTAURANTDRIFT LYNGDAL AS?

Beth Ones is registered as general manager of RESTAURANTDRIFT LYNGDAL AS.

Where is RESTAURANTDRIFT LYNGDAL AS based?

RESTAURANTDRIFT LYNGDAL AS has its business address in Lyngdal.

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.