BIZTRAC BETA
Rental and operating of own or leased real estate

CHERI AS

Org. no. 924193042 Limited company (AS) Sula Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −62,000
Equity NOK 8.1m
Incorporated 2019
Share capital NOK 45,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).

CHERI AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 924193042. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 45,000, divided into 45 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av aksjer, andre verdipapirer, utlånsvirksomhet, prosjektutvikling, herunder erverv og utvikling og forvaltning av faste eiendommer, og deltagelse i andre selskaper og virksomheter som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −62,000
Equity
NOK 8.1m
Est. value
NOK 10.3m

Financial health · 2025

Liquidity
1259.75
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns CHERI AS?

ERIK HAUGEN
CHERI AS
NOK 0 rev. · NOK −62,000 profit

CHERI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHERI AS own?

CHERI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CHERI AS

Who owns CHERI AS?

ERIK HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of CHERI AS?

CHERI AS had revenue of NOK 0 in 2025.

Where is CHERI AS based?

CHERI AS has its business address in Eidsnes.

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.