BIZTRAC BETA
Other real estate activities on a fee or contract basis

KLEIVELAND BYGG & INVEST AS

Org. no. 916274955 Limited company (AS) Osterøy Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 31,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

KLEIVELAND BYGG & INVEST AS is registered as a limited company in Osterøy, Vestland with organisation number 916274955. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eiendomstaksering, eiendomsinvestering og tømrervirksomhet.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 31,000
Est. value
NOK 3.7m

Financial health · 2025

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

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

Who owns KLEIVELAND BYGG & INVEST AS?

HÅVARD HAGA KLEIVELAND
KLEIVELAND BYGG & INVEST AS
· NOK −12,000 profit

KLEIVELAND BYGG & INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KLEIVELAND BYGG & INVEST AS own?

KLEIVELAND BYGG & INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLEIVELAND BYGG & INVEST AS

Who owns KLEIVELAND BYGG & INVEST AS?

HÅVARD HAGA KLEIVELAND is the largest registered owner, with 100.0%.

Who is the general manager of KLEIVELAND BYGG & INVEST AS?

Håvard Haga Kleiveland is registered as general manager of KLEIVELAND BYGG & INVEST AS.

Where is KLEIVELAND BYGG & INVEST AS based?

KLEIVELAND BYGG & INVEST AS has its business address in Lonevåg.

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.