BIZTRAC BETA
COMPANY REGISTER PROFILE
932591855 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

KAOSKOMPANIET AS

Org. no. 932591855 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Equity NOK 36,000
Incorporated 2023
Share capital NOK 30,000

KAOSKOMPANIET AS is registered as a limited company in Bergen, Vestland with organisation number 932591855. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer, andeler i selskap og annet som står i naturlig forbindelse med dette.”.

Key figures · 2025

Equity
NOK 36,000
Est. value
NOK 42,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KAOSKOMPANIET AS?

KAOSKOMPANIET AS

KAOSKOMPANIET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAOSKOMPANIET AS own?

KAOSKOMPANIET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KAOSKOMPANIET AS

Who owns KAOSKOMPANIET AS?

KAI TVERRÅ is the largest registered owner, with 100.0%.

Where is KAOSKOMPANIET AS based?

KAOSKOMPANIET AS has its business address in Bergen.

Property

Business address c/o Kai Tverrå Johan Sverdrups vei 11, 5063 Bergen
Cadastral unit 4601-162/1257/0/0
Building Tomannsbolig, vertikal · 1 unit

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.