biztrac. BETA
COMPANY REGISTER PROFILE
835721302 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

CHO CONSULTING AS

Org. no. 835721302 Limited company (AS) Lillestrøm Incorporated 2025 Active
Revenue 2025 NOK 527,000
Operating profit NOK 84,000
Equity NOK 96,000
Incorporated 2025
Share capital NOK 30,000

CHO CONSULTING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 835721302. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 527,000 in revenue and NOK 84,000 in operating profit.

Key figures · 2025

Revenue
NOK 527,000
▲ +0 %
Operating profit
NOK 84,000
▼ −65 %
Equity
NOK 96,000
▼ −56 %
Est. value
NOK 458,000

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
18.0%
Weak
Equity as a share of total capital

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

Who owns CHO CONSULTING AS?

CHO CONSULTING AS
NOK 527,000 rev. · NOK 84,000 profit

CHO CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHO CONSULTING AS

Who owns CHO CONSULTING AS?

Christina Hovde Olsen is the largest registered owner, with 100.0%.

What is the revenue of CHO CONSULTING AS?

CHO CONSULTING AS had revenue of NOK 527,000 in 2025.

Who is the general manager of CHO CONSULTING AS?

Christina Hovde Olsen is registered as general manager of CHO CONSULTING AS.

Where is CHO CONSULTING AS based?

CHO CONSULTING AS has its business address in Skedsmokorset.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.