BIZTRAC BETA
Construction of residential and non-residential buildings

KVEHAUGEN BYGG AS

Org. no. 976065379 Limited company (AS) Eidsvoll Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK −106,000
Equity NOK 448,000
Incorporated 1996
Share capital NOK 150,000

Signals

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

KVEHAUGEN BYGG AS is registered as a limited company in Eidsvoll, Akershus with organisation number 976065379. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1996. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Salg og oppsetting av boliger, samt reparasjon og vedlikeholdsarbeide på bygninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK −106,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK −106,000
Equity
NOK 448,000
Est. value
NOK 856,000

Financial health · 2024

Liquidity
1.91
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.4%
Good
Equity as a share of total capital

Who owns KVEHAUGEN BYGG AS?

KJELL ARNE KVEHAUGEN
KVEHAUGEN BYGG AS
NOK 3.4m rev. · NOK −106,000 profit

KVEHAUGEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVEHAUGEN BYGG AS

Who owns KVEHAUGEN BYGG AS?

KJELL ARNE KVEHAUGEN is the largest registered owner, with 100.0%.

What is the revenue of KVEHAUGEN BYGG AS?

KVEHAUGEN BYGG AS had revenue of NOK 3.4m in 2024.

Who is the general manager of KVEHAUGEN BYGG AS?

Kjell Arne Kvehaugen is registered as general manager of KVEHAUGEN BYGG AS.

Where is KVEHAUGEN BYGG AS based?

KVEHAUGEN BYGG AS has its business address in Eidsvoll.

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.