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

GUDBRANDSDAL BILBERGING AS

Org. no. 975996093 Limited company (AS) Dovre Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 27.3m
Operating profit NOK 2.1m
Equity NOK 7.4m
Incorporated 1996
Employees 19
Share capital NOK 435,000

GUDBRANDSDAL BILBERGING AS is registered as a limited company in Dovre, Innlandet with organisation number 975996093. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 1996 and has 19 registered employees. Registered share capital is NOK 435,000, divided into 100 shares. The company's stated purpose is: “Bilberging, service, samt virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.3m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 27.3m
Operating profit
NOK 2.1m
Equity
NOK 7.4m
Est. value
NOK 10.7m

Financial health · 2024

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

Who owns GUDBRANDSDAL BILBERGING AS?

ESPEN THORESEN
GUDBRANDSDAL BILBERGING AS
NOK 27.3m rev. · NOK 2.1m profit

GUDBRANDSDAL BILBERGING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GUDBRANDSDAL BILBERGING AS

Who owns GUDBRANDSDAL BILBERGING AS?

ESPEN THORESEN is the largest registered owner, with 59.0%.

What is the revenue of GUDBRANDSDAL BILBERGING AS?

GUDBRANDSDAL BILBERGING AS had revenue of NOK 27.3m in 2024.

Who is the general manager of GUDBRANDSDAL BILBERGING AS?

Espen Thoresen is registered as general manager of GUDBRANDSDAL BILBERGING AS.

Where is GUDBRANDSDAL BILBERGING AS based?

GUDBRANDSDAL BILBERGING AS has its business address in Dombås.

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.