biztrac. BETA
COMPANY REGISTER PROFILE
983495001 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

OLA B TRANSPORT AS

Org. no. 983495001 Limited company (AS) Røros Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK −342,000
Equity NOK 10.6m
Incorporated 2001
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−342k kr).

OLA B TRANSPORT AS is registered as a limited company in Røros, Trøndelag with organisation number 983495001. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport og entreprenørvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK −342,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
▼ −22 %
Operating profit
NOK −342,000
▼ −168 %
Equity
NOK 10.6m
▼ −4 %
Est. value
NOK 6.9m

Financial health · 2025

Liquidity
3.57
Very good
Current assets ÷ current liabilities
Profitability
-1.3%
Not satisfactory
Return on total assets
Solidity
82.5%
Very good
Equity as a share of total capital

Who owns OLA B TRANSPORT AS?

OLA B TRANSPORT AS
NOK 5.1m rev. · NOK −342,000 profit

OLA B TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OLA B TRANSPORT AS

Who owns OLA B TRANSPORT AS?

Steffen Brynhildsvoll is the largest registered owner, with 99.0%.

What is the revenue of OLA B TRANSPORT AS?

OLA B TRANSPORT AS had revenue of NOK 5.1m in 2025.

Who is the general manager of OLA B TRANSPORT AS?

Steffen Brynhildsvoll is registered as general manager of OLA B TRANSPORT AS.

Where is OLA B TRANSPORT AS based?

OLA B TRANSPORT AS has its business address in Glåmos.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.