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

KAYAL AS

Org. no. 928132196 Limited company (AS) Rælingen Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 331,000
Incorporated 2021
Share capital NOK 50,000

Signals

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

KAYAL AS is registered as a limited company in Rælingen, Akershus with organisation number 928132196. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investering i aksjer og andre produkter/tjenester som naturlig hører sammen med dette.”.

Key figures · 2025

Operating profit
NOK −9,000
▼ −1 %
Equity
NOK 331,000
▲ +49 %
Est. value
NOK 894,000

Financial health · 2025

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

Who owns KAYAL AS?

KAYAL AS
· NOK −9,000 profit

KAYAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAYAL AS own?

KAYAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KAYAL AS

Who owns KAYAL AS?

KAY-ARNE LANGERUD is the largest registered owner, with 100.0%.

Where is KAYAL AS based?

KAYAL AS has its business address in Rælingen.

Property

Business address Stormyrvegen 40, 2005 Rælingen
Cadastral unit 3224-104/531/0/0
Building Enebolig · 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.