BIZTRAC BETA
Freight transport by road

DRIV ENERGI HALLINGDAL AS

Org. no. 981897145 Limited company (AS) Gol Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 240.6m
Operating profit NOK 7.0m
Equity NOK 12.1m
Incorporated 2000
Employees 5
Share capital NOK 100,000

DRIV ENERGI HALLINGDAL AS is registered as a limited company in Gol, Buskerud with organisation number 981897145. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2000 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport av oljeprodukter og alt som står i forbindelse med dette - herunder transport av andre produkter, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 240.6m in revenue and NOK 7.0m in operating profit.

Key figures · 2025

Revenue
NOK 240.6m
Operating profit
NOK 7.0m
Equity
NOK 12.1m
Est. value
NOK 28.6m

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.0%
Good
Equity as a share of total capital

Who owns DRIV ENERGI HALLINGDAL AS?

DRIV AS
DRIV ENERGI HALLINGDAL AS
NOK 240.6m rev. · NOK 7.0m profit

DRIV ENERGI HALLINGDAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRIV ENERGI HALLINGDAL AS

Who owns DRIV ENERGI HALLINGDAL AS?

DRIV AS is the largest registered owner, with 50.0%.

What is the revenue of DRIV ENERGI HALLINGDAL AS?

DRIV ENERGI HALLINGDAL AS had revenue of NOK 240.6m in 2025.

Who is the general manager of DRIV ENERGI HALLINGDAL AS?

Vidar Sletto is registered as general manager of DRIV ENERGI HALLINGDAL AS.

Where is DRIV ENERGI HALLINGDAL AS based?

DRIV ENERGI HALLINGDAL AS has its business address in Gol.

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.