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

STEINHAUG & KLEVEN AS

Org. no. 989974211 Limited company (AS) Notodden Incorporated 2006 Active
Revenue 2025 NOK 18.0m
Operating profit NOK 927,000
Equity NOK 3.7m
Incorporated 2006
Employees 10
Share capital NOK 350,000

STEINHAUG & KLEVEN AS is registered as a limited company in Notodden, Telemark with organisation number 989974211. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2006 and has 10 registered employees. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.0m in revenue and NOK 927,000 in operating profit.

Key figures · 2025

Revenue
NOK 18.0m
▼ −16 %
Operating profit
NOK 927,000
▼ −50 %
Equity
NOK 3.7m
▲ +5 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
1.82
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
49.2%
Very good
Equity as a share of total capital

Who owns STEINHAUG & KLEVEN AS?

STEINHAUG & KLEVEN AS
NOK 18.0m rev. · NOK 927,000 profit

STEINHAUG & KLEVEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STEINHAUG & KLEVEN AS

Who owns STEINHAUG & KLEVEN AS?

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

What is the revenue of STEINHAUG & KLEVEN AS?

STEINHAUG & KLEVEN AS had revenue of NOK 18.0m in 2025.

Who is the general manager of STEINHAUG & KLEVEN AS?

Rune Kleven is registered as general manager of STEINHAUG & KLEVEN AS.

Where is STEINHAUG & KLEVEN AS based?

STEINHAUG & KLEVEN AS has its business address in Notodden.

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.