BIZTRAC BETA
Retail sale of automotive fuel

HOTVEDT DRIFT AS

Org. no. 965212663 Limited company (AS) Asker Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 387.2m
Operating profit NOK −5.6m
Equity NOK 4.2m
Incorporated 1992
Employees 66
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5,6 mill kr).

HOTVEDT DRIFT AS is registered as a limited company in Asker, Akershus with organisation number 965212663. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 1992 and has 66 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Handel, og alt som står i forbindelse hermed, samt deltagelse i annen virksomhet, herunder investering i aksjer, verdipapirer, selskaper, fast eiendom mv.”. The most recent filed accounts, for the 2024 financial year, show NOK 387.2m in revenue and NOK −5.6m in operating profit.

Key figures · 2024

Revenue
NOK 387.2m
Operating profit
NOK −5.6m
Equity
NOK 4.2m
Est. value
NOK 113.4m

Financial health · 2024

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

Who owns HOTVEDT DRIFT AS?

HOTVEDT HOLDING AS
HOTVEDT DRIFT AS
NOK 387.2m rev. · NOK −5.6m profit

HOTVEDT DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOTVEDT DRIFT AS

Who owns HOTVEDT DRIFT AS?

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

What is the revenue of HOTVEDT DRIFT AS?

HOTVEDT DRIFT AS had revenue of NOK 387.2m in 2024.

Who is the general manager of HOTVEDT DRIFT AS?

Hans Petter Hotvedt is registered as general manager of HOTVEDT DRIFT AS.

Where is HOTVEDT DRIFT AS based?

HOTVEDT DRIFT AS has its business address in Hvalstad.

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.