BIZTRAC BETA
Construction of utility projects for fluids

KJELL HOVDA AS

Org. no. 929370783 Limited company (AS) Øvre Eiker Incorporated 1980 Active
Ownership graph ↗
Revenue 2025 NOK 130,000
Operating profit NOK −196,000
Equity NOK 966,000
Incorporated 1980
Share capital NOK 100,000

Signals

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

KJELL HOVDA AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 929370783. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 1980. Registered share capital is NOK 100,000. The company's stated purpose is: “Anleggsarbeide, transport, kjøp/salg av maskiner, biler, utstyr, eiendommer, konsulenttjenester, rådgivning, bistands og reportasjearbeider samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 130,000 in revenue and NOK −196,000 in operating profit.

Key figures · 2025

Revenue
NOK 130,000
Operating profit
NOK −196,000
Equity
NOK 966,000
Est. value
NOK 461,000

Financial health · 2025

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

Who owns KJELL HOVDA AS?

KJELL HOVDA
KJELL HOVDA AS
NOK 130,000 rev. · NOK −196,000 profit

KJELL HOVDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJELL HOVDA AS

Who owns KJELL HOVDA AS?

KJELL HOVDA is the largest registered owner, with 100.0%.

What is the revenue of KJELL HOVDA AS?

KJELL HOVDA AS had revenue of NOK 130,000 in 2025.

Who is the general manager of KJELL HOVDA AS?

Kjell Hovda is registered as general manager of KJELL HOVDA AS.

Where is KJELL HOVDA AS based?

KJELL HOVDA AS has its business address in Vestfossen.

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.