BIZTRAC BETA
Wholesale of other household goods

PROVERN AS

Org. no. 928513750 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 10.0m
Operating profit NOK 2.6m
Equity NOK 4.2m
Incorporated 2021
Employees 6
Share capital NOK 30,000

PROVERN AS is registered as a limited company in Stavanger, Rogaland with organisation number 928513750. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Import, utvikling, produksjon og salg av verneutstyr, personlig verneutstyr (PPE), sikkerhetsprodukter og tilhørende tjenester, samt virksomhet som naturlig står i forbindelse med dette. Selskapet kan også delta i andre selskaper, foreta investeringer og drive nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.0m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 10.0m
Operating profit
NOK 2.6m
Equity
NOK 4.2m
Est. value
NOK 10.3m

Financial health · 2024

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

Who owns PROVERN AS?

GAUTE JOHANNESEN
PROVERN AS
NOK 10.0m rev. · NOK 2.6m profit

PROVERN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROVERN AS

Who owns PROVERN AS?

GAUTE JOHANNESEN is the largest registered owner, with 100.0%.

What is the revenue of PROVERN AS?

PROVERN AS had revenue of NOK 10.0m in 2024.

Who is the general manager of PROVERN AS?

Gaute Johannesen is registered as general manager of PROVERN AS.

Where is PROVERN AS based?

PROVERN AS has its business address in Stavanger.

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.