BIZTRAC BETA
Computer consultancy and computer facilities management activities

PROEXEC AS

Org. no. 932854791 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 104,000
Operating profit NOK −195,000
Equity NOK 50,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−195k kr).

PROEXEC AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932854791. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 104,000 in revenue and NOK −195,000 in operating profit.

Key figures · 2025

Revenue
NOK 104,000
Operating profit
NOK −195,000
Equity
NOK 50,000
Est. value
NOK 198,000

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.0%
Weak
Equity as a share of total capital

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

Who owns PROEXEC AS?

SVEIN CATO WINTHER
PROEXEC AS
NOK 104,000 rev. · NOK −195,000 profit

PROEXEC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROEXEC AS

Who owns PROEXEC AS?

SVEIN CATO WINTHER is the largest registered owner, with 100.0%.

What is the revenue of PROEXEC AS?

PROEXEC AS had revenue of NOK 104,000 in 2025.

Who is the general manager of PROEXEC AS?

Svein Cato Winther is registered as general manager of PROEXEC AS.

Where is PROEXEC AS based?

PROEXEC AS has its business address in Fetsund.

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.