BIZTRAC BETA
Restaurant activities

CAFE TOSCANA ØYER AS

Org. no. 918566325 Limited company (AS) Øyer Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 74,000
Equity NOK 2.2m
Incorporated 2017
Employees 10
Share capital NOK 100,000

CAFE TOSCANA ØYER AS is registered as a limited company in Øyer, Innlandet with organisation number 918566325. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Restaurantvirksomhet, herunder produksjon av tyrkiske og italienske matretter, bakeretter og desserter samt det som naturlig hører til herunder deltakelse i andre selskaper og virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 74,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 74,000
Equity
NOK 2.2m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns CAFE TOSCANA ØYER AS?

MUSTAFA MURAT
CAFE TOSCANA ØYER AS
NOK 7.5m rev. · NOK 74,000 profit

CAFE TOSCANA ØYER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAFE TOSCANA ØYER AS

Who owns CAFE TOSCANA ØYER AS?

MUSTAFA MURAT is the largest registered owner, with 50.0%.

What is the revenue of CAFE TOSCANA ØYER AS?

CAFE TOSCANA ØYER AS had revenue of NOK 7.5m in 2024.

Who is the general manager of CAFE TOSCANA ØYER AS?

Yahya Murat is registered as general manager of CAFE TOSCANA ØYER AS.

Where is CAFE TOSCANA ØYER AS based?

CAFE TOSCANA ØYER AS has its business address in Øyer.

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.