BIZTRAC BETA
Materials recovery

KEBA INVEST AS

Org. no. 826716002 Limited company (AS) Åsnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Equity NOK 30,000
Incorporated 2021
Share capital NOK 30,000

KEBA INVEST AS is registered as a limited company in Åsnes, Innlandet with organisation number 826716002. The business is classified under materials recovery (NACE 38.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue.

Key figures · 2024

Revenue
NOK 10,000
Equity
NOK 30,000
Est. value
NOK 32,000

Financial health · 2024

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

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

Who owns KEBA INVEST AS?

EDGAR DØNÅSEN
KEBA INVEST AS
NOK 10,000 rev.

KEBA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KEBA INVEST AS own?

KEBA INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KEBA INVEST AS

Who owns KEBA INVEST AS?

EDGAR DØNÅSEN is the largest registered owner, with 100.0%.

What is the revenue of KEBA INVEST AS?

KEBA INVEST AS had revenue of NOK 10,000 in 2024.

Who is the general manager of KEBA INVEST AS?

Edgar Dønåsen is registered as general manager of KEBA INVEST AS.

Where is KEBA INVEST AS based?

KEBA INVEST AS has its business address in Flisa.

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.