BIZTRAC BETA
Retail sale of other food

Ø. AARBAKKE AS

Org. no. 979475853 Limited company (AS) Bergen Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 75,000
Operating profit NOK 25,000
Equity NOK −168,000
Incorporated 1997
Share capital NOK 100,000

Signals

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

Ø. AARBAKKE AS is registered as a limited company in Bergen, Vestland with organisation number 979475853. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 20 shares. The company's stated purpose is: “Salg av dagligvarer, vinråstoffer samt hva dermed står i forbindelse, herunder delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 75,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 75,000
Operating profit
NOK 25,000
Equity
NOK −168,000
Est. value
NOK 131,000

Financial health · 2024

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

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

Who owns Ø. AARBAKKE AS?

ØYVIND AARBAKKE
Ø. AARBAKKE AS
NOK 75,000 rev. · NOK 25,000 profit

Ø. AARBAKKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Ø. AARBAKKE AS

Who owns Ø. AARBAKKE AS?

ØYVIND AARBAKKE is the largest registered owner, with 100.0%.

What is the revenue of Ø. AARBAKKE AS?

Ø. AARBAKKE AS had revenue of NOK 75,000 in 2025.

Who is the general manager of Ø. AARBAKKE AS?

Øyvind Aarbakke is registered as general manager of Ø. AARBAKKE AS.

Where is Ø. AARBAKKE AS based?

Ø. AARBAKKE AS has its business address in Sandsli.

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.