biztrac. BETA
COMPANY REGISTER PROFILE
931845748 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

KEBA KAPITAL INVEST AS

Org. no. 931845748 Limited company (AS) Færder Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −322,000
Equity NOK 44.8m
Incorporated 2023
Share capital NOK 600,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−322k kr).

KEBA KAPITAL INVEST AS is registered as a limited company in Færder, Vestfold with organisation number 931845748. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investeringer i aksjer, obligasjoner, selskapsandeler, verdipapirer og annen virksomhet, selv eller gjennom hel- eller deleide selskaper.”.

Key figures · 2025

Operating profit
NOK −322,000
▲ +5 %
Equity
NOK 44.8m
▲ +4 %
Est. value
NOK 46.2m

Financial health · 2025

Liquidity
81.43
Very good
Current assets ÷ current liabilities
Profitability
6.9%
Satisfactory
Return on total assets
Solidity
78.9%
Very good
Equity as a share of total capital

Who owns KEBA KAPITAL INVEST AS?

KEBA KAPITAL INVEST AS
· NOK −322,000 profit

KEBA KAPITAL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KEBA KAPITAL INVEST AS own?

KEBA KAPITAL INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about KEBA KAPITAL INVEST AS

Who owns KEBA KAPITAL INVEST AS?

KEBA HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of KEBA KAPITAL INVEST AS?

Ketil Bakkejord is registered as general manager of KEBA KAPITAL INVEST AS.

Where is KEBA KAPITAL INVEST AS based?

KEBA KAPITAL INVEST AS has its business address in Hvasser.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.