BIZTRAC BETA
Rental and operating of own or leased real estate

KJELSNES EIENDOM AS

Org. no. 919662832 Limited company (AS) Haugesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 783,000
Operating profit NOK 553,000
Equity NOK 1.3m
Incorporated 2017
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KJELSNES EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 919662832. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom samt kjøp og salg av aksjer eller drive annen virksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 783,000 in revenue and NOK 553,000 in operating profit.

Key figures · 2025

Revenue
NOK 783,000
Operating profit
NOK 553,000
Equity
NOK 1.3m
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.6%
Good
Equity as a share of total capital

Who owns KJELSNES EIENDOM AS?

KJELSNES HOLDING AS
KJELSNES EIENDOM AS
NOK 783,000 rev. · NOK 553,000 profit

KJELSNES EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJELSNES EIENDOM AS

Who owns KJELSNES EIENDOM AS?

KJELSNES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KJELSNES EIENDOM AS?

KJELSNES EIENDOM AS had revenue of NOK 783,000 in 2025.

Where is KJELSNES EIENDOM AS based?

KJELSNES EIENDOM AS has its business address in Haugesund.

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.