BIZTRAC BETA
Restaurant activities

CAFÉ SØRØST AS

Org. no. 829302802 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −464,000
Equity NOK −838,000
Incorporated 2022
Employees 9
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−838k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−464k kr).

CAFÉ SØRØST AS is registered as a limited company in Drammen, Buskerud with organisation number 829302802. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg og servering. Drift av kafe og restaurantdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −464,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −464,000
Equity
NOK −838,000

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-63.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns CAFÉ SØRØST AS?

ZEID SHERPOUR
CAFÉ SØRØST AS
NOK 1.9m rev. · NOK −464,000 profit

CAFÉ SØRØST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAFÉ SØRØST AS

Who owns CAFÉ SØRØST AS?

ZEID SHERPOUR is the largest registered owner, with 50.0%.

What is the revenue of CAFÉ SØRØST AS?

CAFÉ SØRØST AS had revenue of NOK 1.9m in 2024.

Who is the general manager of CAFÉ SØRØST AS?

Yaser Abdullah Sherpour is registered as general manager of CAFÉ SØRØST AS.

Where is CAFÉ SØRØST AS based?

CAFÉ SØRØST AS has its business address in Drammen.

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.