biztrac. BETA
COMPANY REGISTER PROFILE
928169022 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

KLEVEN BYGG & ANLEGG AS

Org. no. 928169022 Limited company (AS) Gol Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 42,000
Equity NOK 620,000
Incorporated 2021
Share capital NOK 30,000

KLEVEN BYGG & ANLEGG AS is registered as a limited company in Gol, Buskerud with organisation number 928169022. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utføring av bygg og anleggstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 42,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
▲ +4 %
Operating profit
NOK 42,000
▼ −71 %
Equity
NOK 620,000
▲ +6 %
Est. value
NOK 569,000

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
5.4%
Weak
Return on total assets
Solidity
67.3%
Very good
Equity as a share of total capital

Who owns KLEVEN BYGG & ANLEGG AS?

KLEVEN BYGG & ANLEGG AS
NOK 3.6m rev. · NOK 42,000 profit

KLEVEN BYGG & ANLEGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLEVEN BYGG & ANLEGG AS

Who owns KLEVEN BYGG & ANLEGG AS?

Lars Kleven is the largest registered owner, with 50.0%.

What is the revenue of KLEVEN BYGG & ANLEGG AS?

KLEVEN BYGG & ANLEGG AS had revenue of NOK 3.6m in 2025.

Who is the general manager of KLEVEN BYGG & ANLEGG AS?

Bjørn Kleven is registered as general manager of KLEVEN BYGG & ANLEGG AS.

Where is KLEVEN BYGG & ANLEGG AS based?

KLEVEN BYGG & ANLEGG AS has its business address in Gol.

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.