BIZTRAC BETA
Restaurant activities

SAKAYA HAMMERFEST AS

Org. no. 998432383 Limited company (AS) Hammerfest Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 16.8m
Operating profit NOK 1.5m
Equity NOK 2.2m
Incorporated 2012
Employees 21
Share capital NOK 380,000

SAKAYA HAMMERFEST AS is registered as a limited company in Hammerfest, Finnmark with organisation number 998432383. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 21 registered employees. Registered share capital is NOK 380,000, divided into 380 shares. The company's stated purpose is: “Å eie og drive restaurant, pub, bar og annen aktivitet som passer inn i lokalene, kjøp og salg av aksjer og annet som naturlig hører inn under foranstående. Selskapet kan delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.8m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 16.8m
Operating profit
NOK 1.5m
Equity
NOK 2.2m
Est. value
NOK 6.5m

Financial health · 2024

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

Who owns SAKAYA HAMMERFEST AS?

SAM LIU
SAKAYA HAMMERFEST AS
NOK 16.8m rev. · NOK 1.5m profit

SAKAYA HAMMERFEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAKAYA HAMMERFEST AS

Who owns SAKAYA HAMMERFEST AS?

SAM LIU is the largest registered owner, with 64.2%.

What is the revenue of SAKAYA HAMMERFEST AS?

SAKAYA HAMMERFEST AS had revenue of NOK 16.8m in 2024.

Who is the general manager of SAKAYA HAMMERFEST AS?

Sam Liu is registered as general manager of SAKAYA HAMMERFEST AS.

Where is SAKAYA HAMMERFEST AS based?

SAKAYA HAMMERFEST AS has its business address in Hammerfest.

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.