BIZTRAC BETA
Repair and maintenance of motor vehicles

OPPLAND TUNGBILSERVICE AS

Org. no. 982787602 Limited company (AS) Nord-Aurdal Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 26.2m
Operating profit NOK 3.1m
Equity NOK 5.7m
Incorporated 2000
Employees 13
Share capital NOK 2.0m

OPPLAND TUNGBILSERVICE AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 982787602. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2000 and has 13 registered employees. Registered share capital is NOK 2.0m, divided into 200 shares. The company's stated purpose is: “Verkstedsdrift for lastebiler, busser og andre kjøretøy og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.2m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 26.2m
Operating profit
NOK 3.1m
Equity
NOK 5.7m
Est. value
NOK 14.9m

Financial health · 2024

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

Who owns OPPLAND TUNGBILSERVICE AS?

NORSK SCANIA AS
OPPLAND TUNGBILSERVICE AS
NOK 26.2m rev. · NOK 3.1m profit

OPPLAND TUNGBILSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OPPLAND TUNGBILSERVICE AS

Who owns OPPLAND TUNGBILSERVICE AS?

NORSK SCANIA AS is the largest registered owner, with 50.0%.

What is the revenue of OPPLAND TUNGBILSERVICE AS?

OPPLAND TUNGBILSERVICE AS had revenue of NOK 26.2m in 2024.

Who is the general manager of OPPLAND TUNGBILSERVICE AS?

Ove Bakkene Stokkebryn is registered as general manager of OPPLAND TUNGBILSERVICE AS.

Where is OPPLAND TUNGBILSERVICE AS based?

OPPLAND TUNGBILSERVICE AS has its business address in Fagernes.

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.