BIZTRAC BETA
Uoppgitt

KILHAVN INVEST AS

Org. no. 990693420 Limited company (AS) Gjesdal Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 4.0m
Incorporated 2006
Share capital NOK 500,000

Signals

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

KILHAVN INVEST AS is registered as a limited company in Gjesdal, Rogaland with organisation number 990693420. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2006. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Eie og investere i aksjer, andre selskaper og virksomheter, samt investering i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 4.0m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns KILHAVN INVEST AS?

TORSTEIN KILHAVN
KILHAVN INVEST AS
NOK 0 rev. · NOK −26,000 profit

KILHAVN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KILHAVN INVEST AS own?

KILHAVN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KILHAVN INVEST AS

Who owns KILHAVN INVEST AS?

TORSTEIN KILHAVN is the largest registered owner, with 100.0%.

What is the revenue of KILHAVN INVEST AS?

KILHAVN INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of KILHAVN INVEST AS?

Torstein Kilhavn is registered as general manager of KILHAVN INVEST AS.

Where is KILHAVN INVEST AS based?

KILHAVN INVEST AS has its business address in Ålgård.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.