BIZTRAC BETA
Restaurant activities

ØLBU AS

Org. no. 914212944 Limited company (AS) Stavanger Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK −94,000
Equity NOK 867,000
Incorporated 2014
Share capital NOK 32,000

Signals

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

ØLBU AS is registered as a limited company in Stavanger, Rogaland with organisation number 914212944. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014. Registered share capital is NOK 32,000, divided into 790 shares. The company's stated purpose is: “Salg av mat, drikke og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK −94,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK −94,000
Equity
NOK 867,000
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns ØLBU AS?

TOU SCENE AS
ØLBU AS
NOK 6.6m rev. · NOK −94,000 profit

ØLBU AS has 6 registered shareholders:

All shareholders and roles →

Which companies does ØLBU AS own?

ØLBU AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØLBU AS

Who owns ØLBU AS?

TOU SCENE AS is the largest registered owner, with 55.6%.

What is the revenue of ØLBU AS?

ØLBU AS had revenue of NOK 6.6m in 2024.

Who is the general manager of ØLBU AS?

Liam James Devlin is registered as general manager of ØLBU AS.

Where is ØLBU AS based?

ØLBU 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.