BIZTRAC BETA
COMPANY REGISTER PROFILE
976574575 ORG. NO. 2024 ACCOUNTS 10 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

KVARTEN BISTRO AS

Org. no. 976574575 Limited company (AS) Oslo Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −66,000
Equity NOK 33,000
Incorporated 1996
Share capital NOK 100,000

Signals

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

KVARTEN BISTRO AS is registered as a limited company in Oslo, Oslo with organisation number 976574575. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Restaurantdrift og det som måtte stå i forbindelse med slik virksomhet. Selskapet kan gjennom aksje- tegning gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −66,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −66,000
Equity
NOK 33,000
Est. value
NOK 1.4m

Financial health · 2024

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

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

Who owns KVARTEN BISTRO AS?

MOHAMMAD AWAIS AKHTAR
KVARTEN BISTRO AS
NOK 2.0m rev. · NOK −66,000 profit

KVARTEN BISTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVARTEN BISTRO AS

Who owns KVARTEN BISTRO AS?

MOHAMMAD AWAIS AKHTAR is the largest registered owner, with 100.0%.

What is the revenue of KVARTEN BISTRO AS?

KVARTEN BISTRO AS had revenue of NOK 2.0m in 2024.

Where is KVARTEN BISTRO AS based?

KVARTEN BISTRO 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.