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

KJA HOLDING AS

Org. no. 924411333 Limited company (AS) Hamar Incorporated 2019 Active
Ownership graph ↗
Equity NOK 2.8m
Incorporated 2019
Share capital NOK 30,000

KJA HOLDING AS is registered as a limited company in Hamar, Innlandet with organisation number 924411333. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i aksjer og andeler i andre selskaper og fast eiendom, samt annen økonomisk virksomhet.”.

Key figures · 2025

Equity
NOK 2.8m
▼ −12 %
Est. value
NOK 9.9m

Financial health · 2025

Liquidity
47.93
Very good
Current assets ÷ current liabilities
Profitability
42.4%
Very good
Return on total assets
Solidity
98.0%
Very good
Equity as a share of total capital

Who owns KJA HOLDING AS?

KJA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJA HOLDING AS own?

KJA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KJA HOLDING AS

Who owns KJA HOLDING AS?

KNUT JØRGEN ARNSETH is the largest registered owner, with 100.0%.

Who is the general manager of KJA HOLDING AS?

Knut Jørgen Arnseth is registered as general manager of KJA HOLDING AS.

Where is KJA HOLDING AS based?

KJA HOLDING AS has its business address in Ingeberg.

Property

Business address Andreas Karsets veg 5, 2323 Ingeberg
Cadastral unit 3403-63/26/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.