BIZTRAC BETA
Restaurant activities

APROPO AS

Org. no. 924454113 Limited company (AS) Moss Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 137,000
Equity NOK −845,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−845k kr).

APROPO AS is registered as a limited company in Moss, Østfold with organisation number 924454113. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Restaurant og kafedrift og andre produkter og tjenester som naturlig hører sammen med dette, herunder delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 137,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 137,000
Equity
NOK −845,000
Est. value
NOK 1.0m

Financial health · 2024

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

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

Who owns APROPO AS?

ALEXANDRU CUC
APROPO AS
NOK 1.8m rev. · NOK 137,000 profit

APROPO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about APROPO AS

Who owns APROPO AS?

ALEXANDRU CUC is the largest registered owner, with 50.0%.

What is the revenue of APROPO AS?

APROPO AS had revenue of NOK 1.8m in 2024.

Who is the general manager of APROPO AS?

Alexandru Cuc is registered as general manager of APROPO AS.

Where is APROPO AS based?

APROPO AS has its business address in Moss.

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.