BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

CERWE HOLDING AS

Org. no. 996467503 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 210,000
Operating profit NOK 120,000
Equity NOK 1.7m
Incorporated 2011
Share capital NOK 100,000

CERWE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 996467503. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investeringsvirksomhet. Eie og forvalte aksjer, obligasjoner og andre verdipapirer, eie og forvalte eiendom, deltagelse i andre selskaper samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 210,000 in revenue and NOK 120,000 in operating profit.

Key figures · 2025

Revenue
NOK 210,000
Operating profit
NOK 120,000
Equity
NOK 1.7m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns CERWE HOLDING AS?

ØYVIND THORSELL
CERWE HOLDING AS
NOK 210,000 rev. · NOK 120,000 profit

CERWE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CERWE HOLDING AS own?

CERWE HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about CERWE HOLDING AS

Who owns CERWE HOLDING AS?

ØYVIND THORSELL is the largest registered owner, with 100.0%.

What is the revenue of CERWE HOLDING AS?

CERWE HOLDING AS had revenue of NOK 210,000 in 2025.

Where is CERWE HOLDING AS based?

CERWE HOLDING AS has its business address in Oslo.

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.