BIZTRAC BETA
Restaurant activities

MR. LONG RESTAURANT FROLAND AS

Org. no. 931453238 Limited company (AS) Froland Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 353,000
Equity NOK 348,000
Incorporated 2023
Employees 6
Share capital NOK 30,000

MR. LONG RESTAURANT FROLAND AS is registered as a limited company in Froland, Agder with organisation number 931453238. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Restaurantbedrift for salg og servering av norsk og kinamat.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 353,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 353,000
Equity
NOK 348,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.3%
Good
Equity as a share of total capital

Who owns MR. LONG RESTAURANT FROLAND AS?

LINGLING CHEN
MR. LONG RESTAURANT FROLAND AS
NOK 4.3m rev. · NOK 353,000 profit

MR. LONG RESTAURANT FROLAND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MR. LONG RESTAURANT FROLAND AS

Who owns MR. LONG RESTAURANT FROLAND AS?

LINGLING CHEN is the largest registered owner, with 90.0%.

What is the revenue of MR. LONG RESTAURANT FROLAND AS?

MR. LONG RESTAURANT FROLAND AS had revenue of NOK 4.3m in 2025.

Who is the general manager of MR. LONG RESTAURANT FROLAND AS?

Espen Knutsen is registered as general manager of MR. LONG RESTAURANT FROLAND AS.

Where is MR. LONG RESTAURANT FROLAND AS based?

MR. LONG RESTAURANT FROLAND AS has its business address in Froland.

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.