BIZTRAC BETA
Dental practice care activities

WUBA INVEST AS

Org. no. 920485715 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −97,000
Equity NOK 1.9m
Incorporated 2018
Share capital NOK 30,000

Signals

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

WUBA INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 920485715. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og invester i andre selskaper og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −97,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −97,000
Equity
NOK 1.9m
Est. value
NOK 14.6m

Financial health · 2024

Liquidity
2.00
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
64.3%
Very good
Equity as a share of total capital

Who owns WUBA INVEST AS?

WUBA KASSAHUN
WUBA INVEST AS
NOK 0 rev. · NOK −97,000 profit

WUBA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WUBA INVEST AS own?

WUBA INVEST AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about WUBA INVEST AS

Who owns WUBA INVEST AS?

WUBA KASSAHUN is the largest registered owner, with 100.0%.

What is the revenue of WUBA INVEST AS?

WUBA INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of WUBA INVEST AS?

Wuba Kassahun is registered as general manager of WUBA INVEST AS.

Where is WUBA INVEST AS based?

WUBA INVEST AS has its business address in Eiksmarka.

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.