BIZTRAC BETA
Other construction installation

DRIFT TEK AS

Org. no. 920013775 Limited company (AS) Tønsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK −285,000
Equity NOK 418,000
Incorporated 2017
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−285k kr).

DRIFT TEK AS is registered as a limited company in Tønsberg, Vestfold with organisation number 920013775. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “El-installasjoner med handel. Delta i andre selskap med lignende virksomhet, samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK −285,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK −285,000
Equity
NOK 418,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns DRIFT TEK AS?

PER OTTAR HUSEBY
DRIFT TEK AS
NOK 4.0m rev. · NOK −285,000 profit

DRIFT TEK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRIFT TEK AS

Who owns DRIFT TEK AS?

PER OTTAR HUSEBY is the largest registered owner, with 33.3%.

What is the revenue of DRIFT TEK AS?

DRIFT TEK AS had revenue of NOK 4.0m in 2024.

Who is the general manager of DRIFT TEK AS?

Arne Jonny Røe is registered as general manager of DRIFT TEK AS.

Where is DRIFT TEK AS based?

DRIFT TEK AS has its business address in Vear.

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.