BIZTRAC BETA
Restaurant activities

KILEN BRYGGE RESTAURANT AS

Org. no. 993787493 Limited company (AS) Sandefjord Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 15.1m
Operating profit NOK 1.7m
Equity NOK 4.5m
Incorporated 2009
Employees 24
Share capital NOK 100,000

KILEN BRYGGE RESTAURANT AS is registered as a limited company in Sandefjord, Vestfold with organisation number 993787493. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2009 and has 24 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurantvirksomhet og det som hører innunder dette, samt deltagelse i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.1m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 15.1m
Operating profit
NOK 1.7m
Equity
NOK 4.5m
Est. value
NOK 8.8m

Financial health · 2024

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

Who owns KILEN BRYGGE RESTAURANT AS?

ILIR KRUEZIU
KILEN BRYGGE RESTAURANT AS
NOK 15.1m rev. · NOK 1.7m profit

KILEN BRYGGE RESTAURANT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KILEN BRYGGE RESTAURANT AS

Who owns KILEN BRYGGE RESTAURANT AS?

ILIR KRUEZIU is the largest registered owner, with 100.0%.

What is the revenue of KILEN BRYGGE RESTAURANT AS?

KILEN BRYGGE RESTAURANT AS had revenue of NOK 15.1m in 2024.

Who is the general manager of KILEN BRYGGE RESTAURANT AS?

Ilir Krueziu is registered as general manager of KILEN BRYGGE RESTAURANT AS.

Where is KILEN BRYGGE RESTAURANT AS based?

KILEN BRYGGE RESTAURANT AS has its business address in Sandefjord.

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.