BIZTRAC BETA
Construction of utility projects for fluids

BRØNN OG ENERGIBORING BUSKERUD AS

Org. no. 984575270 Limited company (AS) Hole Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 275,000
Equity NOK 1.1m
Incorporated 2002
Share capital NOK 100,000

BRØNN OG ENERGIBORING BUSKERUD AS is registered as a limited company in Hole, Buskerud with organisation number 984575270. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Brønn og energiboring.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 275,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 275,000
Equity
NOK 1.1m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns BRØNN OG ENERGIBORING BUSKERUD AS?

HANS TANDBERG
BRØNN OG ENERGIBORING BUSKERUD AS
NOK 4.5m rev. · NOK 275,000 profit

BRØNN OG ENERGIBORING BUSKERUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRØNN OG ENERGIBORING BUSKERUD AS

Who owns BRØNN OG ENERGIBORING BUSKERUD AS?

HANS TANDBERG is the largest registered owner, with 100.0%.

What is the revenue of BRØNN OG ENERGIBORING BUSKERUD AS?

BRØNN OG ENERGIBORING BUSKERUD AS had revenue of NOK 4.5m in 2024.

Who is the general manager of BRØNN OG ENERGIBORING BUSKERUD AS?

Hans Tandberg is registered as general manager of BRØNN OG ENERGIBORING BUSKERUD AS.

Where is BRØNN OG ENERGIBORING BUSKERUD AS based?

BRØNN OG ENERGIBORING BUSKERUD AS has its business address in Hønefoss.

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.