BIZTRAC BETA
Construction of utility projects for fluids

GUDBRANDSDAL BRØNNBORING AS

Org. no. 939083820 Limited company (AS) Nord-Fron Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 13.1m
Operating profit NOK 1.5m
Equity NOK 7.4m
Incorporated 1986
Employees 8
Share capital NOK 100,000

GUDBRANDSDAL BRØNNBORING AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 939083820. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 1986 and has 8 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Handel, brønnboring, grunnboring, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.1m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 13.1m
Operating profit
NOK 1.5m
Equity
NOK 7.4m
Est. value
NOK 8.3m

Financial health · 2024

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

Who owns GUDBRANDSDAL BRØNNBORING AS?

HENNING BEITDOKKEN
GUDBRANDSDAL BRØNNBORING AS
NOK 13.1m rev. · NOK 1.5m profit

GUDBRANDSDAL BRØNNBORING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GUDBRANDSDAL BRØNNBORING AS

Who owns GUDBRANDSDAL BRØNNBORING AS?

HENNING BEITDOKKEN is the largest registered owner, with 50.0%.

What is the revenue of GUDBRANDSDAL BRØNNBORING AS?

GUDBRANDSDAL BRØNNBORING AS had revenue of NOK 13.1m in 2024.

Who is the general manager of GUDBRANDSDAL BRØNNBORING AS?

Henning Beitdokken is registered as general manager of GUDBRANDSDAL BRØNNBORING AS.

Where is GUDBRANDSDAL BRØNNBORING AS based?

GUDBRANDSDAL BRØNNBORING AS has its business address in Kvam.

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.