BIZTRAC BETA
Freight transport by road

OLA BERGUM TRANSPORT OG VERKSTED AS

Org. no. 989998706 Limited company (AS) Østre Toten Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 46,000
Equity NOK 1.6m
Incorporated 2006
Share capital NOK 100,000

OLA BERGUM TRANSPORT OG VERKSTED AS is registered as a limited company in Østre Toten, Innlandet with organisation number 989998706. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Godstransport på vei.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 46,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 46,000
Equity
NOK 1.6m
Est. value
NOK 967,000

Financial health · 2024

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

Who owns OLA BERGUM TRANSPORT OG VERKSTED AS?

OLA BERGUM
OLA BERGUM TRANSPORT OG VERKSTED AS
NOK 2.0m rev. · NOK 46,000 profit

OLA BERGUM TRANSPORT OG VERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLA BERGUM TRANSPORT OG VERKSTED AS

Who owns OLA BERGUM TRANSPORT OG VERKSTED AS?

OLA BERGUM is the largest registered owner, with 100.0%.

What is the revenue of OLA BERGUM TRANSPORT OG VERKSTED AS?

OLA BERGUM TRANSPORT OG VERKSTED AS had revenue of NOK 2.0m in 2024.

Who is the general manager of OLA BERGUM TRANSPORT OG VERKSTED AS?

Ola Bergum is registered as general manager of OLA BERGUM TRANSPORT OG VERKSTED AS.

Where is OLA BERGUM TRANSPORT OG VERKSTED AS based?

OLA BERGUM TRANSPORT OG VERKSTED AS has its business address in Kolbu.

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.