BIZTRAC BETA
Restaurant activities

KOMPIS AMANDA AS

Org. no. 929404017 Limited company (AS) Haugesund Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK −7.6m
Equity NOK −1.4m
Incorporated 2022
Share capital NOK 200,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7,6 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KOMPIS AMANDA AS is registered as a limited company in Haugesund, Rogaland with organisation number 929404017. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Serveringsvirksomhet, og dermed alt som står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK −7.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK −7.6m
Equity
NOK −1.4m

Financial health · 2024

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.0%
Weak
Equity as a share of total capital

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

Who owns KOMPIS AMANDA AS?

KOMPIS NORGE AS
KOMPIS AMANDA AS
NOK 3.1m rev. · NOK −7.6m profit

KOMPIS AMANDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOMPIS AMANDA AS

Who owns KOMPIS AMANDA AS?

KOMPIS NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of KOMPIS AMANDA AS?

KOMPIS AMANDA AS had revenue of NOK 3.1m in 2024.

Where is KOMPIS AMANDA AS based?

KOMPIS AMANDA AS has its business address in Haugesund.

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.