BIZTRAC BETA
Freight transport by road

INNLANDET BETONGPUMPING AS

Org. no. 874349992 Limited company (AS) Etnedal Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 35.1m
Operating profit NOK 8.8m
Equity NOK 1.7m
Incorporated 1995
Share capital NOK 102,000

INNLANDET BETONGPUMPING AS is registered as a limited company in Etnedal, Innlandet with organisation number 874349992. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1995. Registered share capital is NOK 102,000, divided into 51 shares. The company's stated purpose is: “Betongtransport og hva herved står i naturlig forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.1m in revenue and NOK 8.8m in operating profit.

Key figures · 2024

Revenue
NOK 35.1m
Operating profit
NOK 8.8m
Equity
NOK 1.7m
Est. value
NOK 26.1m

Financial health · 2024

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

Who owns INNLANDET BETONGPUMPING AS?

DENNIS WAHLEMBERG
INNLANDET BETONGPUMPING AS
NOK 35.1m rev. · NOK 8.8m profit

INNLANDET BETONGPUMPING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

INNLANDET BETONGPUMPING AS er morselskap for 1 datterselskap:

Frequently asked questions about INNLANDET BETONGPUMPING AS

Who owns INNLANDET BETONGPUMPING AS?

DENNIS WAHLEMBERG is the largest registered owner, with 100.0%.

What is the revenue of INNLANDET BETONGPUMPING AS?

INNLANDET BETONGPUMPING AS had revenue of NOK 35.1m in 2024.

Who is the general manager of INNLANDET BETONGPUMPING AS?

Dennis Wahlemberg is registered as general manager of INNLANDET BETONGPUMPING AS.

Where is INNLANDET BETONGPUMPING AS based?

INNLANDET BETONGPUMPING AS has its business address in Etnedal.

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.