BIZTRAC BETA
Restaurant activities

U2 CAFE DRIFT AS

Org. no. 995158914 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 17.9m
Operating profit NOK −779,000
Equity NOK 374,000
Incorporated 2010
Employees 28
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−779k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

U2 CAFE DRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 995158914. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2010 and has 28 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Restaurant.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.9m in revenue and NOK −779,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.9m
Operating profit
NOK −779,000
Equity
NOK 374,000
Est. value
NOK 12.4m

Financial health · 2024

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns U2 CAFE DRIFT AS?

E & G INVEST AS
U2 CAFE DRIFT AS
NOK 17.9m rev. · NOK −779,000 profit

U2 CAFE DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about U2 CAFE DRIFT AS

Who owns U2 CAFE DRIFT AS?

E & G INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of U2 CAFE DRIFT AS?

U2 CAFE DRIFT AS had revenue of NOK 17.9m in 2024.

Who is the general manager of U2 CAFE DRIFT AS?

Güner Kaya is registered as general manager of U2 CAFE DRIFT AS.

Where is U2 CAFE DRIFT AS based?

U2 CAFE DRIFT AS has its business address in Oslo.

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.