BIZTRAC BETA
Other postal and courier activities

ROLAND TRANSPORT AS

Org. no. 912159965 Limited company (AS) Notodden Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −176,000
Equity NOK 503,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

ROLAND TRANSPORT AS is registered as a limited company in Notodden, Telemark with organisation number 912159965. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Transport, samt annen virksomhet som står i naturlig tilknytning til dette. Selskapet kan videre eie aksjer i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −176,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −176,000
Equity
NOK 503,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns ROLAND TRANSPORT AS?

BJØRN ROLAND
ROLAND TRANSPORT AS
NOK 2.2m rev. · NOK −176,000 profit

ROLAND TRANSPORT AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROLAND TRANSPORT AS

Who owns ROLAND TRANSPORT AS?

BJØRN ROLAND is the largest registered owner, with 26.0%.

What is the revenue of ROLAND TRANSPORT AS?

ROLAND TRANSPORT AS had revenue of NOK 2.2m in 2025.

Who is the general manager of ROLAND TRANSPORT AS?

Bjørn Roland is registered as general manager of ROLAND TRANSPORT AS.

Where is ROLAND TRANSPORT AS based?

ROLAND TRANSPORT AS has its business address in Notodden.

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.