BIZTRAC BETA
Other education activities

CHOHAN LEVEL CONSULTING AS

Org. no. 930542822 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 506,000
Operating profit NOK 267,000
Equity NOK 231,000
Incorporated 2022
Share capital NOK 30,000

CHOHAN LEVEL CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 930542822. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal selge tjenester og varer innen konsulent inom salg, ledarskap, motivasjon og inspiration. - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 506,000 in revenue and NOK 267,000 in operating profit.

Key figures · 2024

Revenue
NOK 506,000
Operating profit
NOK 267,000
Equity
NOK 231,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns CHOHAN LEVEL CONSULTING AS?

KAMEL555 HOLDING AS
CHOHAN LEVEL CONSULTING AS
NOK 506,000 rev. · NOK 267,000 profit

CHOHAN LEVEL CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHOHAN LEVEL CONSULTING AS

Who owns CHOHAN LEVEL CONSULTING AS?

KAMEL555 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of CHOHAN LEVEL CONSULTING AS?

CHOHAN LEVEL CONSULTING AS had revenue of NOK 506,000 in 2024.

Where is CHOHAN LEVEL CONSULTING AS based?

CHOHAN LEVEL CONSULTING 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.