BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

PROVDRIFT AS

Org. no. 921859643 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −128,000
Equity NOK 509,000
Incorporated 2018
Share capital NOK 800,000

Signals

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

PROVDRIFT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921859643. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2018. Registered share capital is NOK 800,000, divided into 800 shares. The company's stated purpose is: “Utleie av bygg og anleggsutstyr, maskiner og verktøy, samt rigg og drift, og tjenester i tilknytning av dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −128,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −128,000
Equity
NOK 509,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns PROVDRIFT AS?

TOM KENNETH FOSSEN
PROVDRIFT AS
NOK 1.2m rev. · NOK −128,000 profit

PROVDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROVDRIFT AS

Who owns PROVDRIFT AS?

TOM KENNETH FOSSEN is the largest registered owner, with 100.0%.

What is the revenue of PROVDRIFT AS?

PROVDRIFT AS had revenue of NOK 1.2m in 2024.

Who is the general manager of PROVDRIFT AS?

Tom Kenneth Fossen is registered as general manager of PROVDRIFT AS.

Where is PROVDRIFT AS based?

PROVDRIFT AS has its business address in Heimdal.

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.