BIZTRAC BETA
Business and other management consultancy activities

BAKKEBO AS

Org. no. 927876221 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK −31,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−31k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

BAKKEBO AS is registered as a limited company in Skien, Telemark with organisation number 927876221. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer, samt annen virksomhet som står i nær sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK −31,000

Financial health · 2025

Liquidity
11.70
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.2%
Weak
Equity as a share of total capital

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

Who owns BAKKEBO AS?

Ben Roger Elvenes
BAKKEBO AS
NOK 0 rev. · NOK −16,000 profit

BAKKEBO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BAKKEBO AS own?

BAKKEBO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BAKKEBO AS

Who owns BAKKEBO AS?

Ben Roger Elvenes is the largest registered owner, with 100.0%.

What is the revenue of BAKKEBO AS?

BAKKEBO AS had revenue of NOK 0 in 2025.

Where is BAKKEBO AS based?

BAKKEBO AS has its business address in Skien.

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.