biztrac. BETA
COMPANY REGISTER PROFILE
928540650 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Industrial product and fashion design activities

CARELESS AS

Org. no. 928540650 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 146.2m
Operating profit NOK 24.1m
Equity NOK 7.1m
Incorporated 2022
Employees 55
Share capital NOK 33,000

CARELESS AS is registered as a limited company in Kristiansand, Agder with organisation number 928540650. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2022 and has 55 registered employees. Registered share capital is NOK 33,000, divided into 3000 shares. The company's stated purpose is: “Designe og produsere moteartikler for videresalg og annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 146.2m in revenue and NOK 24.1m in operating profit.

Former names: AFAS 10122-30 AS

Key figures · 2025

Revenue
NOK 146.2m
▲ +8 %
Operating profit
NOK 24.1m
▲ +59 %
Equity
NOK 7.1m
▲ +96 %
Est. value
NOK 112.6m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
53.3%
Very good
Return on total assets
Solidity
16.0%
Satisfactory
Equity as a share of total capital

Who owns CARELESS AS?

CARELESS AS
NOK 146.2m rev. · NOK 24.1m profit

CARELESS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CARELESS AS

Who owns CARELESS AS?

SARAAEMILIEE AS is the largest registered owner, with 50.0%.

What is the revenue of CARELESS AS?

CARELESS AS had revenue of NOK 146.2m in 2025.

Who is the general manager of CARELESS AS?

Vegard Skau Tjønnås is registered as general manager of CARELESS AS.

Where is CARELESS AS based?

CARELESS AS has its business address in Kristiansand S.

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.