biztrac. BETA
COMPANY REGISTER PROFILE
916056435 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

KOMPA INVEST AS

Org. no. 916056435 Limited company (AS) Lyngdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1.9m
Equity NOK 2.1m
Incorporated 2015
Share capital NOK 2.5m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,9 mill kr).

KOMPA INVEST AS is registered as a limited company in Lyngdal, Agder with organisation number 916056435. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 2.5m, divided into 40 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, eiendomsutvikling samt virksomhet som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1.9m in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1.9m
▼ −319 %
Equity
NOK 2.1m
▼ −50 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
-27.2%
Not satisfactory
Return on total assets
Solidity
33.7%
Good
Equity as a share of total capital

Who owns KOMPA INVEST AS?

KOMPA INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KOMPA INVEST AS own?

KOMPA INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KOMPA INVEST AS

Who owns KOMPA INVEST AS?

WEINTRAUB AS is the largest registered owner, with 25.0%.

What is the revenue of KOMPA INVEST AS?

KOMPA INVEST AS had revenue of NOK 0 in 2025.

Where is KOMPA INVEST AS based?

KOMPA INVEST AS has its business address in Lyngdal.

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

Report a problem

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