BIZTRAC BETA
COMPANY REGISTER PROFILE
912878120 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

PROSOLVE HOLDING AS

Org. no. 912878120 Limited company (AS) Stryn Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −45,000
Equity NOK −760,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−760k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−45k kr).

PROSOLVE HOLDING AS is registered as a limited company in Stryn, Vestland with organisation number 912878120. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Erverve og eie eierandeler i andre selskaper samt hva som måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −45,000
▼ −262 %
Equity
NOK −760,000
▼ −6 %

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
-399.6%
Not satisfactory
Return on total assets
Solidity
-13409.1%
Weak
Equity as a share of total capital

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

Who owns PROSOLVE HOLDING AS?

PROSOLVE HOLDING AS
NOK 0 rev. · NOK −45,000 profit

PROSOLVE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROSOLVE HOLDING AS

Who owns PROSOLVE HOLDING AS?

CLAUS DAAE LAMPE is the largest registered owner, with 100.0%.

What is the revenue of PROSOLVE HOLDING AS?

PROSOLVE HOLDING AS had revenue of NOK 0 in 2025.

Where is PROSOLVE HOLDING AS based?

PROSOLVE HOLDING AS has its business address in Stryn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.