biztrac. BETA
COMPANY REGISTER PROFILE
920853498 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Bankrupt UPDATED 03.10.2026
⚠KILEHAUGEN AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Development of building projects

KILEHAUGEN AS

Org. no. 920853498 Limited company (AS) Sandnes Incorporated 2018 Bankrupt
Ownership graph ↗
Operating profit NOK −187,000
Equity NOK −1.7m
Incorporated 2018
Share capital NOK 1.5m

Signals

3 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−187k kr).

KILEHAUGEN AS is registered as a limited company in Sandnes, Rogaland with organisation number 920853498. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 1.5m, divided into 300 shares. The company's stated purpose is: “Kjøp og salg, samt utvikling av fast eiendom, samt investeringer i selskaper med tilsvarende og tilknyttet virksomhet.”.

Key figures · 2024

Operating profit
NOK −187,000
▼ −229 %
Equity
NOK −1.7m
▼ −392 %

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.2%
Not satisfactory
Return on total assets
Solidity
-10.8%
Weak
Equity as a share of total capital

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

Who owns KILEHAUGEN AS?

KILEHAUGEN AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KILEHAUGEN AS

Who owns KILEHAUGEN AS?

EIENDOM- OG TOMTEUTVIKLING AS is the largest registered owner, with 29.3%.

Who is the general manager of KILEHAUGEN AS?

Kjell Sigve Fiskebekk is registered as general manager of KILEHAUGEN AS.

Where is KILEHAUGEN AS based?

KILEHAUGEN AS has its business address in Hommersåk.

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

Report a problem

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