BIZTRAC BETA
COMPANY REGISTER PROFILE
991872299 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

CAMM AS

Org. no. 991872299 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 156,000
Operating profit NOK −148,000
Equity NOK 29.5m
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−148k kr).
  • Nylig endring 2026-08-09 Adresseendring registrert 2026-08-09.

CAMM AS is registered as a limited company in Oslo, Oslo with organisation number 991872299. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringer i verdipapirer, eiendom, samt deltakelse i virksomhet med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 156,000 in revenue and NOK −148,000 in operating profit.

Key figures · 2024

Revenue
NOK 156,000
Operating profit
NOK −148,000
Equity
NOK 29.5m
Est. value
NOK 25.0m

Financial health · 2024

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

Who owns CAMM AS?

MIKKEL ØSTBYE
CAMM AS
NOK 156,000 rev. · NOK −148,000 profit

CAMM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CAMM AS

Who owns CAMM AS?

MIKKEL ØSTBYE is the largest registered owner, with 100.0%.

What is the revenue of CAMM AS?

CAMM AS had revenue of NOK 156,000 in 2024.

Who is the general manager of CAMM AS?

Mikkel Østbye is registered as general manager of CAMM AS.

Where is CAMM AS based?

CAMM 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.