BIZTRAC BETA
Uoppgitt

CARMEL INVEST AS

Org. no. 992956879 Limited company (AS) Aurskog-Høland Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −47,000
Equity NOK −2.9m
Incorporated 2008
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−47k kr).

CARMEL INVEST AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 992956879. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og fast eiendom og alt som står i forbindelse med det.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −47,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −47,000
Equity
NOK −2.9m

Financial health · 2024

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

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

Who owns CARMEL INVEST AS?

MORTEN KALLEBERG BREIBY
CARMEL INVEST AS
NOK 0 rev. · NOK −47,000 profit

CARMEL INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CARMEL INVEST AS

Who owns CARMEL INVEST AS?

MORTEN KALLEBERG BREIBY is the largest registered owner, with 68.0%.

What is the revenue of CARMEL INVEST AS?

CARMEL INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of CARMEL INVEST AS?

Welley Husvik is registered as general manager of CARMEL INVEST AS.

Where is CARMEL INVEST AS based?

CARMEL INVEST AS has its business address in Fosser.

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.