BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

TUROTEKNIKK DRIFT AS

Org. no. 999322743 Limited company (AS) Bærum Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 35.0m
Operating profit NOK 6.2m
Equity NOK 11.8m
Incorporated 2012
Employees 11
Share capital NOK 2.0m

TUROTEKNIKK DRIFT AS is registered as a limited company in Bærum, Akershus with organisation number 999322743. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2012 and has 11 registered employees. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Prosjektering, handel, eksport/import, erverv og drift av fast eiendom og annen økonomisk virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.0m in revenue and NOK 6.2m in operating profit.

Key figures · 2024

Revenue
NOK 35.0m
Operating profit
NOK 6.2m
Equity
NOK 11.8m
Est. value
NOK 26.7m

Financial health · 2024

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

Who owns TUROTEKNIKK DRIFT AS?

HILDERTUNET 2 AS
TUROTEKNIKK DRIFT AS
NOK 35.0m rev. · NOK 6.2m profit

TUROTEKNIKK DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUROTEKNIKK DRIFT AS

Who owns TUROTEKNIKK DRIFT AS?

HILDERTUNET 2 AS is the largest registered owner, with 100.0%.

What is the revenue of TUROTEKNIKK DRIFT AS?

TUROTEKNIKK DRIFT AS had revenue of NOK 35.0m in 2024.

Who is the general manager of TUROTEKNIKK DRIFT AS?

Magne Klemmet Løseth is registered as general manager of TUROTEKNIKK DRIFT AS.

Where is TUROTEKNIKK DRIFT AS based?

TUROTEKNIKK DRIFT AS has its business address in Slependen.

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.