BIZTRAC BETA
Construction of roads and motorways

LUDVIG KAMPERHAUG AS

Org. no. 926816179 Limited company (AS) Sarpsborg Incorporated 1980 Active
Ownership graph ↗
Revenue 2025 NOK 34.6m
Operating profit NOK 3.9m
Equity NOK 2.9m
Incorporated 1980
Employees 18
Share capital NOK 54,000

LUDVIG KAMPERHAUG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 926816179. The business is classified under construction of roads and motorways (NACE 42.110). The company was incorporated in 1980 and has 18 registered employees. Registered share capital is NOK 54,000, divided into 27 shares. The company's stated purpose is: “Anleggsvirksomhet av enhver art samt transport av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 34.6m in revenue and NOK 3.9m in operating profit.

Key figures · 2025

Revenue
NOK 34.6m
Operating profit
NOK 3.9m
Equity
NOK 2.9m
Est. value
NOK 12.7m

Financial health · 2025

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

Who owns LUDVIG KAMPERHAUG AS?

NEDRE GLOMMA INVEST AS
LUDVIG KAMPERHAUG AS
NOK 34.6m rev. · NOK 3.9m profit

LUDVIG KAMPERHAUG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LUDVIG KAMPERHAUG AS er morselskap for 1 datterselskap:

Frequently asked questions about LUDVIG KAMPERHAUG AS

Who owns LUDVIG KAMPERHAUG AS?

NEDRE GLOMMA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LUDVIG KAMPERHAUG AS?

LUDVIG KAMPERHAUG AS had revenue of NOK 34.6m in 2025.

Who is the general manager of LUDVIG KAMPERHAUG AS?

Espen Kristoffer Kamperhaug is registered as general manager of LUDVIG KAMPERHAUG AS.

Where is LUDVIG KAMPERHAUG AS based?

LUDVIG KAMPERHAUG AS has its business address in Grålum.

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.