BIZTRAC BETA
COMPANY REGISTER PROFILE
997811208 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

KLEPP BISTRO AS

Org. no. 997811208 Limited company (AS) Klepp Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK 195,000
Equity NOK 275,000
Incorporated 2011
Employees 5
Share capital NOK 100,000

KLEPP BISTRO AS is registered as a limited company in Klepp, Rogaland with organisation number 997811208. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2011 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Restaurantvirksomhet, herunder produksjon av tyrkiske, italienske, amerikanske og norske matretter, samt bakervarer og desserter og alt som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK 195,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK 195,000
Equity
NOK 275,000
Est. value
NOK 864,000

Financial health · 2024

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

Who owns KLEPP BISTRO AS?

IMDAT YASAR
KLEPP BISTRO AS
NOK 5.7m rev. · NOK 195,000 profit

KLEPP BISTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLEPP BISTRO AS

Who owns KLEPP BISTRO AS?

IMDAT YASAR is the largest registered owner, with 100.0%.

What is the revenue of KLEPP BISTRO AS?

KLEPP BISTRO AS had revenue of NOK 5.7m in 2024.

Who is the general manager of KLEPP BISTRO AS?

Imdat Yasar is registered as general manager of KLEPP BISTRO AS.

Where is KLEPP BISTRO AS based?

KLEPP BISTRO AS has its business address in Kleppe.

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.