BIZTRAC BETA
Restaurant activities

BILO AS

Org. no. 922292558 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 736,000
Equity NOK −704,000
Incorporated 2019
Employees 13
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−704k kr).

BILO AS is registered as a limited company in Oslo, Oslo with organisation number 922292558. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av restaurant, salg av selskapsmat og dertil hørende virksomhet. Videre utleie av leide og eide lokaler innen bolig og næring, samt deltakelse og investering i alt som naturlig faller innenfor dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 736,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 736,000
Equity
NOK −704,000
Est. value
NOK 4.3m

Financial health · 2024

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-46.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BILO AS?

BILAL OCAG
BILO AS
NOK 7.5m rev. · NOK 736,000 profit

BILO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILO AS

Who owns BILO AS?

BILAL OCAG is the largest registered owner, with 100.0%.

What is the revenue of BILO AS?

BILO AS had revenue of NOK 7.5m in 2024.

Who is the general manager of BILO AS?

Aleksander Mustafa Helin Ocag is registered as general manager of BILO AS.

Where is BILO AS based?

BILO 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.