BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

NEXTPRO AS

Org. no. 934082281 Limited company (AS) Gjøvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 129,000
Operating profit NOK 13,000
Equity NOK 36,000
Incorporated 2024
Share capital NOK 30,000

NEXTPRO AS is registered as a limited company in Gjøvik, Innlandet with organisation number 934082281. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen klær, sko og utstyr via netthandel - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 129,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2024

Revenue
NOK 129,000
Operating profit
NOK 13,000
Equity
NOK 36,000
Est. value
NOK 63,000

Financial health · 2024

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

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

Who owns NEXTPRO AS?

MARIUS ENGEN VEISTEN
NEXTPRO AS
NOK 129,000 rev. · NOK 13,000 profit

NEXTPRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NEXTPRO AS

Who owns NEXTPRO AS?

MARIUS ENGEN VEISTEN is the largest registered owner, with 50.0%.

What is the revenue of NEXTPRO AS?

NEXTPRO AS had revenue of NOK 129,000 in 2024.

Who is the general manager of NEXTPRO AS?

Marius Engen Veisten is registered as general manager of NEXTPRO AS.

Where is NEXTPRO AS based?

NEXTPRO AS has its business address in Biri.

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.