biztrac. BETA
COMPANY REGISTER PROFILE
994593145 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

K BY KAOS AS

Org. no. 994593145 Limited company (AS) Lørenskog Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 11.7m
Operating profit NOK −706,000
Equity NOK 2.5m
Incorporated 2009
Employees 17
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−706k kr).

K BY KAOS AS is registered as a limited company in Lørenskog, Akershus with organisation number 994593145. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2009 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Detaljhandel med klær samt deltakelse i andre selskaper med samme virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.7m in revenue and NOK −706,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.7m
▼ −5 %
Operating profit
NOK −706,000
▼ −5899 %
Equity
NOK 2.5m
▼ −23 %
Est. value
NOK 5.0m

Financial health · 2025

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
-10.3%
Not satisfactory
Return on total assets
Solidity
40.4%
Very good
Equity as a share of total capital

Who owns K BY KAOS AS?

K BY KAOS AS
NOK 11.7m rev. · NOK −706,000 profit

K BY KAOS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about K BY KAOS AS

Who owns K BY KAOS AS?

Jay Monge is the largest registered owner, with 50.0%.

What is the revenue of K BY KAOS AS?

K BY KAOS AS had revenue of NOK 11.7m in 2025.

Who is the general manager of K BY KAOS AS?

Jay Monge is registered as general manager of K BY KAOS AS.

Where is K BY KAOS AS based?

K BY KAOS AS has its business address in Lørenskog.

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.