BIZTRAC BETA
Rental and operating of own or leased real estate

JHN EIENDOM AS

Org. no. 991309721 Limited company (AS) Klepp Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 793,000
Equity NOK 6.1m
Incorporated 2007
Share capital NOK 100,000

JHN EIENDOM AS is registered as a limited company in Klepp, Rogaland with organisation number 991309721. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i og utleie av eiendom og hva hermed står i forbindelse, direkte eller via deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 793,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 793,000
Equity
NOK 6.1m
Est. value
NOK 5.9m

Financial health · 2025

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

Who owns JHN EIENDOM AS?

JAN HÅKON NORDBØ
JHN EIENDOM AS
NOK 1.1m rev. · NOK 793,000 profit

JHN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JHN EIENDOM AS own?

JHN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JHN EIENDOM AS

Who owns JHN EIENDOM AS?

JAN HÅKON NORDBØ is the largest registered owner, with 100.0%.

What is the revenue of JHN EIENDOM AS?

JHN EIENDOM AS had revenue of NOK 1.1m in 2025.

Who is the general manager of JHN EIENDOM AS?

Jan Håkon Nordbø is registered as general manager of JHN EIENDOM AS.

Where is JHN EIENDOM AS based?

JHN EIENDOM AS has its business address in Klepp Stasjon.

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.