BIZTRAC BETA
Restaurant activities

BESTEKOMPIS AS

Org. no. 925297208 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK −273,000
Equity NOK 147,000
Incorporated 2020
Employees 12
Share capital NOK 30,000

Signals

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

BESTEKOMPIS AS is registered as a limited company in Oslo, Oslo with organisation number 925297208. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive mat- og alkoholservering og restaurantdrift, med salg av tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK −273,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK −273,000
Equity
NOK 147,000
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns BESTEKOMPIS AS?

ABADUL HOQUE
BESTEKOMPIS AS
NOK 8.5m rev. · NOK −273,000 profit

BESTEKOMPIS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BESTEKOMPIS AS

Who owns BESTEKOMPIS AS?

ABADUL HOQUE is the largest registered owner, with 28.4%.

What is the revenue of BESTEKOMPIS AS?

BESTEKOMPIS AS had revenue of NOK 8.5m in 2024.

Who is the general manager of BESTEKOMPIS AS?

Kabinjit Singh is registered as general manager of BESTEKOMPIS AS.

Where is BESTEKOMPIS AS based?

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