BIZTRAC BETA
COMPANY REGISTER PROFILE
936508103 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Hairdressing and barber activities

KAM2 AS

Org. no. 936508103 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK 0
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-27.

KAM2 AS is registered as a limited company in Oslo, Oslo with organisation number 936508103. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Frisering og annen skjønnhetspleie. Samt annen virksomhet som hører hertil eller tjener aksjonærenes interesser.”.

Key figures · 2025

Operating profit
NOK 0

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

Who owns KAM2 AS?

KAM2 AS
· NOK 0 profit

KAM2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAM2 AS

Who owns KAM2 AS?

KAM NORGE AS is the largest registered owner, with 100.0%.

Who is the general manager of KAM2 AS?

Yasser Mebarek is registered as general manager of KAM2 AS.

Where is KAM2 AS based?

KAM2 AS has its business address in Oslo.

Property

Business address Trygve Lies plass 1, 1051 Oslo
Cadastral unit 301-105/707/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

45 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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