BIZTRAC BETA
Business and other management consultancy activities

CLAIRON Z AS

Org. no. 936410308 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 208,000
Operating profit NOK 177,000
Equity NOK 168,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-10.

CLAIRON Z AS is registered as a limited company in Oslo, Oslo with organisation number 936410308. 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 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen bedriftsrådgivning og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 208,000 in revenue and NOK 177,000 in operating profit.

Key figures · 2025

Revenue
NOK 208,000
Operating profit
NOK 177,000
Equity
NOK 168,000
Est. value
NOK 670,000

Financial health · 2025

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

Who owns CLAIRON Z AS?

KRISTIAN MØRK SPETALEN
CLAIRON Z AS
NOK 208,000 rev. · NOK 177,000 profit

CLAIRON Z AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CLAIRON Z AS

Who owns CLAIRON Z AS?

KRISTIAN MØRK SPETALEN is the largest registered owner, with 100.0%.

What is the revenue of CLAIRON Z AS?

CLAIRON Z AS had revenue of NOK 208,000 in 2025.

Who is the general manager of CLAIRON Z AS?

Kristian Mørk Spetalen is registered as general manager of CLAIRON Z AS.

Where is CLAIRON Z AS based?

CLAIRON Z 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.