BIZTRAC BETA
Manufacture of other articles of paper and paperboard

MCC STAVANGER AS

Org. no. 975989348 Limited company (AS) Stavanger Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 124.8m
Operating profit NOK 10.1m
Equity NOK 106.0m
Incorporated 1995
Employees 39
Share capital NOK 775,000

MCC STAVANGER AS is registered as a limited company in Stavanger, Rogaland with organisation number 975989348. The business is classified under manufacture of other articles of paper and paperboard (NACE 17.250). The company was incorporated in 1995 and has 39 registered employees. Registered share capital is NOK 775,000, divided into 775000 shares. The company's stated purpose is: “Trykkerivirksomhet, kjøp og salg av maskiner, varer og etiketter, agenturer, deltakelse i andre selskaper og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 124.8m in revenue and NOK 10.1m in operating profit.

Key figures · 2024

Revenue
NOK 124.8m
Operating profit
NOK 10.1m
Equity
NOK 106.0m
Est. value
NOK 107.7m

Financial health · 2024

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

Who owns MCC STAVANGER AS?

MCC VERSTRAETE N.V.
MCC STAVANGER AS
NOK 124.8m rev. · NOK 10.1m profit

MCC STAVANGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MCC STAVANGER AS

Who owns MCC STAVANGER AS?

MCC VERSTRAETE N.V. is the largest registered owner, with 100.0%.

What is the revenue of MCC STAVANGER AS?

MCC STAVANGER AS had revenue of NOK 124.8m in 2024.

Who is the general manager of MCC STAVANGER AS?

Curth Sven Ola Carlsson is registered as general manager of MCC STAVANGER AS.

Where is MCC STAVANGER AS based?

MCC STAVANGER AS has its business address in Stavanger.

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.