BIZTRAC BETA
COMPANY REGISTER PROFILE
989221701 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

KAGIAN AS

Org. no. 989221701 Limited company (AS) Øygarden Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −49,000
Equity NOK 3.3m
Incorporated 2005
Share capital NOK 100,000

Signals

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

KAGIAN AS is registered as a limited company in Øygarden, Vestland with organisation number 989221701. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet og investering i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −49,000
Equity
NOK 3.3m
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns KAGIAN AS?

KAGIAN AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAGIAN AS

Who owns KAGIAN AS?

ANDRE RONG is the largest registered owner, with 31.0%.

Who is the general manager of KAGIAN AS?

Gisle Kårbø Rong is registered as general manager of KAGIAN AS.

Where is KAGIAN AS based?

KAGIAN AS has its business address in Rong.

Property

Business address Myrane 3, 5337 Rong
Cadastral unit 4626-242/107/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

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.