BIZTRAC BETA
Other manufacturing n.e.c.

KOMPO AS

Org. no. 926039865 Limited company (AS) Tønsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −19,000
Equity NOK −969,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−969k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

KOMPO AS is registered as a limited company in Tønsberg, Vestfold with organisation number 926039865. The business is classified under other manufacturing n.e.c. (NACE 32.990). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon, utvikling og salg av komposittprodukter og dertil hørende produkter og produksjonsutstyr, samt å søke agenturer innenfor samme produktområde.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK −969,000

Financial health · 2024

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

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

Who owns KOMPO AS?

GUDMUNDSEN & MOESTUE AS
KOMPO AS
NOK 0 rev. · NOK −19,000 profit

KOMPO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOMPO AS

Who owns KOMPO AS?

GUDMUNDSEN & MOESTUE AS is the largest registered owner, with 80.0%.

What is the revenue of KOMPO AS?

KOMPO AS had revenue of NOK 0 in 2024.

Who is the general manager of KOMPO AS?

John-Patrick Gudmundsen is registered as general manager of KOMPO AS.

Where is KOMPO AS based?

KOMPO AS has its business address in Barkåker.

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.