BIZTRAC BETA
Restaurant activities

MR CREOSOTE & FRIENDS AS

Org. no. 919900865 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 1.8m
Equity NOK 900,000
Incorporated 2017
Employees 11
Share capital NOK 30,000

MR CREOSOTE & FRIENDS AS is registered as a limited company in Bergen, Vestland with organisation number 919900865. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive restaurant og virksomhet som faller naturlig sammen med dette. Selskapet skal også kunne foreta investeringer og forvalte eierinteresser i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 1.8m
Equity
NOK 900,000
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns MR CREOSOTE & FRIENDS AS?

EGLE STOCKUTE
MR CREOSOTE & FRIENDS AS
NOK 7.6m rev. · NOK 1.8m profit

MR CREOSOTE & FRIENDS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MR CREOSOTE & FRIENDS AS

Who owns MR CREOSOTE & FRIENDS AS?

EGLE STOCKUTE is the largest registered owner, with 50.0%.

What is the revenue of MR CREOSOTE & FRIENDS AS?

MR CREOSOTE & FRIENDS AS had revenue of NOK 7.6m in 2024.

Who is the general manager of MR CREOSOTE & FRIENDS AS?

Egle Stockute is registered as general manager of MR CREOSOTE & FRIENDS AS.

Where is MR CREOSOTE & FRIENDS AS based?

MR CREOSOTE & FRIENDS AS has its business address in Bergen.

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.