BIZTRAC BETA
Other services incidental to land transport n.e.c.

OPPDAL BILBERGING AS

Org. no. 983196837 Limited company (AS) Oppdal Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 1.4m
Equity NOK 1.9m
Incorporated 2001
Employees 9
Share capital NOK 30,000

OPPDAL BILBERGING AS is registered as a limited company in Oppdal, Trøndelag with organisation number 983196837. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2001 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bilberging, veihjelp og transport, samt annen virksomhet som naturlig hører sammen med dette, herunder investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 1.4m
Equity
NOK 1.9m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns OPPDAL BILBERGING AS?

KLETTHAMMER HOLDING AS
OPPDAL BILBERGING AS
NOK 8.5m rev. · NOK 1.4m profit

OPPDAL BILBERGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPPDAL BILBERGING AS

Who owns OPPDAL BILBERGING AS?

KLETTHAMMER HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OPPDAL BILBERGING AS?

OPPDAL BILBERGING AS had revenue of NOK 8.5m in 2024.

Who is the general manager of OPPDAL BILBERGING AS?

Njord Kletthammer is registered as general manager of OPPDAL BILBERGING AS.

Where is OPPDAL BILBERGING AS based?

OPPDAL BILBERGING AS has its business address in Oppdal.

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.