BIZTRAC BETA
Freight transport by road

SKJEBERG BETONGPUMPING AS

Org. no. 965642676 Limited company (AS) Kristiansand Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 273,000
Operating profit NOK 33,000
Equity NOK 257,000
Incorporated 1992
Share capital NOK 100,000

SKJEBERG BETONGPUMPING AS is registered as a limited company in Kristiansand, Agder with organisation number 965642676. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport av betong og sidestilte produkter. Videre ved aksjebesittelse eller på annen måte gjøre seg interessert i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 273,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 273,000
Operating profit
NOK 33,000
Equity
NOK 257,000
Est. value
NOK 254,000

Financial health · 2025

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

Who owns SKJEBERG BETONGPUMPING AS?

VIDAR TORE JENSEN
SKJEBERG BETONGPUMPING AS
NOK 273,000 rev. · NOK 33,000 profit

SKJEBERG BETONGPUMPING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKJEBERG BETONGPUMPING AS

Who owns SKJEBERG BETONGPUMPING AS?

VIDAR TORE JENSEN is the largest registered owner, with 66.0%.

What is the revenue of SKJEBERG BETONGPUMPING AS?

SKJEBERG BETONGPUMPING AS had revenue of NOK 273,000 in 2025.

Who is the general manager of SKJEBERG BETONGPUMPING AS?

Vidar Tore Jensen is registered as general manager of SKJEBERG BETONGPUMPING AS.

Where is SKJEBERG BETONGPUMPING AS based?

SKJEBERG BETONGPUMPING AS has its business address in Søgne.

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.