BIZTRAC BETA
Civil engineering activities

PROVTEK AS

Org. no. 923536043 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 786,000
Operating profit NOK 149,000
Equity NOK −106,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−106k kr).

PROVTEK AS is registered as a limited company in Oslo, Oslo with organisation number 923536043. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen bygg og anlegg - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 786,000 in revenue and NOK 149,000 in operating profit.

Key figures · 2025

Revenue
NOK 786,000
Operating profit
NOK 149,000
Equity
NOK −106,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-40.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PROVTEK AS?

AMIR SHAHZAD ALI SHAH
PROVTEK AS
NOK 786,000 rev. · NOK 149,000 profit

PROVTEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROVTEK AS

Who owns PROVTEK AS?

AMIR SHAHZAD ALI SHAH is the largest registered owner, with 100.0%.

What is the revenue of PROVTEK AS?

PROVTEK AS had revenue of NOK 786,000 in 2025.

Who is the general manager of PROVTEK AS?

Amir Shahzad Ali Shah is registered as general manager of PROVTEK AS.

Where is PROVTEK AS based?

PROVTEK AS has its business address in Oslo.

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.