BIZTRAC BETA
Restaurant activities

CAFE SJØBRIS AS

Org. no. 920197299 Limited company (AS) Porsgrunn Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 10.5m
Incorporated 2017
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).

CAFE SJØBRIS AS is registered as a limited company in Porsgrunn, Telemark with organisation number 920197299. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Investering i serveringsvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 10.5m
Est. value
NOK 11.1m

Financial health · 2025

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

Who owns CAFE SJØBRIS AS?

JORUNN ISAKSEN
CAFE SJØBRIS AS
NOK 0 rev. · NOK −38,000 profit

CAFE SJØBRIS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CAFE SJØBRIS AS own?

CAFE SJØBRIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CAFE SJØBRIS AS

Who owns CAFE SJØBRIS AS?

JORUNN ISAKSEN is the largest registered owner, with 75.0%.

What is the revenue of CAFE SJØBRIS AS?

CAFE SJØBRIS AS had revenue of NOK 0 in 2025.

Who is the general manager of CAFE SJØBRIS AS?

Jorunn Isaksen is registered as general manager of CAFE SJØBRIS AS.

Where is CAFE SJØBRIS AS based?

CAFE SJØBRIS AS has its business address in Porsgrunn.

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.