BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

TORSTEINSEN DRIFT AS

Org. no. 915014755 Limited company (AS) Dyrøy Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 29,000
Equity NOK 492,000
Incorporated 2015
Share capital NOK 30,000

TORSTEINSEN DRIFT AS is registered as a limited company in Dyrøy, Troms with organisation number 915014755. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av egen arbeidskraft til asfaltrelatert virksomhet, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 29,000
Equity
NOK 492,000
Est. value
NOK 410,000

Financial health · 2025

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

Who owns TORSTEINSEN DRIFT AS?

KIM ARNE TORSTEINSEN
TORSTEINSEN DRIFT AS
NOK 1.8m rev. · NOK 29,000 profit

TORSTEINSEN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORSTEINSEN DRIFT AS

Who owns TORSTEINSEN DRIFT AS?

KIM ARNE TORSTEINSEN is the largest registered owner, with 100.0%.

What is the revenue of TORSTEINSEN DRIFT AS?

TORSTEINSEN DRIFT AS had revenue of NOK 1.8m in 2025.

Who is the general manager of TORSTEINSEN DRIFT AS?

Kim Arne Torsteinsen is registered as general manager of TORSTEINSEN DRIFT AS.

Where is TORSTEINSEN DRIFT AS based?

TORSTEINSEN DRIFT AS has its business address in Brøstadbotn.

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.