BIZTRAC BETA
Uoppgitt

KEBACO HOLDING AS

Org. no. 922721777 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 411,000
Incorporated 2019
Share capital NOK 37,000

Signals

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

KEBACO HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 922721777. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 37,000, divided into 36850 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 411,000
Est. value
NOK 319,000

Financial health · 2024

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

Who owns KEBACO HOLDING AS?

TOMMY EGEBERG
KEBACO HOLDING AS
NOK 0 rev. · NOK −9,000 profit

KEBACO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KEBACO HOLDING AS own?

KEBACO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KEBACO HOLDING AS

Who owns KEBACO HOLDING AS?

TOMMY EGEBERG is the largest registered owner, with 100.0%.

What is the revenue of KEBACO HOLDING AS?

KEBACO HOLDING AS had revenue of NOK 0 in 2025.

Where is KEBACO HOLDING AS based?

KEBACO HOLDING AS has its business address in Drammen.

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.