BIZTRAC BETA
Site preparation

KLINGSHEIM AS

Org. no. 986471545 Limited company (AS) Klepp Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 222,000
Equity NOK 8.3m
Incorporated 2004
Share capital NOK 100,000

KLINGSHEIM AS is registered as a limited company in Klepp, Rogaland with organisation number 986471545. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Maskinentreprenør, graving av grøfter, transportoppdrag og det som medfølger dette. Markedsføring og salg av reklame vedrørende drift av komersiell motorsportaktivitet, samt det som medfølger dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 222,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 222,000
Equity
NOK 8.3m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns KLINGSHEIM AS?

ODD ERLING KLINGSHEIM
KLINGSHEIM AS
NOK 2.6m rev. · NOK 222,000 profit

KLINGSHEIM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KLINGSHEIM AS own?

KLINGSHEIM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLINGSHEIM AS

Who owns KLINGSHEIM AS?

ODD ERLING KLINGSHEIM is the largest registered owner, with 100.0%.

What is the revenue of KLINGSHEIM AS?

KLINGSHEIM AS had revenue of NOK 2.6m in 2025.

Who is the general manager of KLINGSHEIM AS?

Odd Erling Klingsheim is registered as general manager of KLINGSHEIM AS.

Where is KLINGSHEIM AS based?

KLINGSHEIM AS has its business address in Klepp Stasjon.

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.