BIZTRAC BETA
Restaurant activities

TIGER SUSHI BAR BODØ AS

Org. no. 931136399 Limited company (AS) Bodø Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 23.8m
Operating profit NOK −8,000
Equity NOK 2.2m
Incorporated 2023
Employees 23
Share capital NOK 830,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).

TIGER SUSHI BAR BODØ AS is registered as a limited company in Bodø, Nordland with organisation number 931136399. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 23 registered employees. Registered share capital is NOK 830,000, divided into 30000 shares. The company's stated purpose is: “Servering av mat og drikke, samt det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.8m in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 23.8m
Operating profit
NOK −8,000
Equity
NOK 2.2m
Est. value
NOK 17.8m

Financial health · 2024

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

Who owns TIGER SUSHI BAR BODØ AS?

TSBB AS
TIGER SUSHI BAR BODØ AS
NOK 23.8m rev. · NOK −8,000 profit

TIGER SUSHI BAR BODØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TIGER SUSHI BAR BODØ AS

Who owns TIGER SUSHI BAR BODØ AS?

TSBB AS is the largest registered owner, with 100.0%.

What is the revenue of TIGER SUSHI BAR BODØ AS?

TIGER SUSHI BAR BODØ AS had revenue of NOK 23.8m in 2024.

Who is the general manager of TIGER SUSHI BAR BODØ AS?

Panudech Junpengpen is registered as general manager of TIGER SUSHI BAR BODØ AS.

Where is TIGER SUSHI BAR BODØ AS based?

TIGER SUSHI BAR BODØ AS has its business address in Bodø.

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.