BIZTRAC BETA
Freight transport by road

OSLO BETONGTRANSPORT AS

Org. no. 999169961 Limited company (AS) Nes Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 20.5m
Operating profit NOK 493,000
Equity NOK 1.3m
Incorporated 2012
Employees 7
Share capital NOK 30,000

OSLO BETONGTRANSPORT AS is registered as a limited company in Nes, Akershus with organisation number 999169961. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2012 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Være totaltilbyder av betongtransport i Oslo og omegn samt delta i virksomhet med beslektet type aktivitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.5m in revenue and NOK 493,000 in operating profit.

Key figures · 2025

Revenue
NOK 20.5m
Operating profit
NOK 493,000
Equity
NOK 1.3m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns OSLO BETONGTRANSPORT AS?

WOJCIECH MAREK BERNACKI
OSLO BETONGTRANSPORT AS
NOK 20.5m rev. · NOK 493,000 profit

OSLO BETONGTRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO BETONGTRANSPORT AS

Who owns OSLO BETONGTRANSPORT AS?

WOJCIECH MAREK BERNACKI is the largest registered owner, with 100.0%.

What is the revenue of OSLO BETONGTRANSPORT AS?

OSLO BETONGTRANSPORT AS had revenue of NOK 20.5m in 2025.

Who is the general manager of OSLO BETONGTRANSPORT AS?

Wojciech Marek Bernacki is registered as general manager of OSLO BETONGTRANSPORT AS.

Where is OSLO BETONGTRANSPORT AS based?

OSLO BETONGTRANSPORT AS has its business address in Årnes.

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.