BIZTRAC BETA
Restaurant activities

NEW WAABARI RESTAURANT AS

Org. no. 916879237 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK 89,000
Equity NOK 470,000
Incorporated 2016
Employees 9
Share capital NOK 200,000

NEW WAABARI RESTAURANT AS is registered as a limited company in Oslo, Oslo with organisation number 916879237. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016 and has 9 registered employees. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Restaurant- og serveringsdrift samt hva som herved står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK 89,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK 89,000
Equity
NOK 470,000
Est. value
NOK 569,000

Financial health · 2024

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

Who owns NEW WAABARI RESTAURANT AS?

BILLE AHMED MOHAMOUD
NEW WAABARI RESTAURANT AS
NOK 10.7m rev. · NOK 89,000 profit

NEW WAABARI RESTAURANT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEW WAABARI RESTAURANT AS

Who owns NEW WAABARI RESTAURANT AS?

BILLE AHMED MOHAMOUD is the largest registered owner, with 100.0%.

What is the revenue of NEW WAABARI RESTAURANT AS?

NEW WAABARI RESTAURANT AS had revenue of NOK 10.7m in 2024.

Who is the general manager of NEW WAABARI RESTAURANT AS?

Abdiasiz Ali Jimaali is registered as general manager of NEW WAABARI RESTAURANT AS.

Where is NEW WAABARI RESTAURANT AS based?

NEW WAABARI RESTAURANT 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.