BIZTRAC BETA
Restaurant activities

SEOUL SØSTRE AS

Org. no. 932066033 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −18,000
Equity NOK 1.4m
Incorporated 2023
Employees 6
Share capital NOK 33,000

Signals

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

SEOUL SØSTRE AS is registered as a limited company in Stavanger, Rogaland with organisation number 932066033. 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 33,000, divided into 30000 shares. The company's stated purpose is: “Restaurantvirksomhet og alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −18,000
Equity
NOK 1.4m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns SEOUL SØSTRE AS?

SEOUL HOLDING AS
SEOUL SØSTRE AS
NOK 1.4m rev. · NOK −18,000 profit

SEOUL SØSTRE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SEOUL SØSTRE AS er morselskap for 1 datterselskap:

Frequently asked questions about SEOUL SØSTRE AS

Who owns SEOUL SØSTRE AS?

SEOUL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SEOUL SØSTRE AS?

SEOUL SØSTRE AS had revenue of NOK 1.4m in 2024.

Who is the general manager of SEOUL SØSTRE AS?

Simen Sæten is registered as general manager of SEOUL SØSTRE AS.

Where is SEOUL SØSTRE AS based?

SEOUL SØSTRE AS has its business address in Stavanger.

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.