BIZTRAC BETA
Office administrative and support activities

CC PARTNER LILLESTRØM AS

Org. no. 889067292 Limited company (AS) Lillestrøm Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK 227,000
Equity NOK 1.3m
Incorporated 2005
Share capital NOK 100,000

CC PARTNER LILLESTRØM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 889067292. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Dokument- og presentasjonsproduksjon, tjenester knyttet til dette og konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK 227,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK 227,000
Equity
NOK 1.3m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns CC PARTNER LILLESTRØM AS?

THOMAS MAXIMILIAN LIGAARDEN
CC PARTNER LILLESTRØM AS
NOK 6.9m rev. · NOK 227,000 profit

CC PARTNER LILLESTRØM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CC PARTNER LILLESTRØM AS

Who owns CC PARTNER LILLESTRØM AS?

THOMAS MAXIMILIAN LIGAARDEN is the largest registered owner, with 60.0%.

What is the revenue of CC PARTNER LILLESTRØM AS?

CC PARTNER LILLESTRØM AS had revenue of NOK 6.9m in 2024.

Who is the general manager of CC PARTNER LILLESTRØM AS?

Thomas Maximilian Ligaarden is registered as general manager of CC PARTNER LILLESTRØM AS.

Where is CC PARTNER LILLESTRØM AS based?

CC PARTNER LILLESTRØM AS has its business address in Lillestrøm.

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.