BIZTRAC BETA
Rental and operating of own or leased real estate

JULNES EIENDOM AS

Org. no. 976285654 Limited company (AS) Kinn Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 965,000
Equity NOK 27.6m
Incorporated 1996
Share capital NOK 450,000

JULNES EIENDOM AS is registered as a limited company in Kinn, Vestland with organisation number 976285654. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 450,000, divided into 4500 shares. The company's stated purpose is: “Kjøpe, opparbeide og selge eiendommer, videre å anskaffe driftsmidler for eget bruk og utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 965,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 965,000
Equity
NOK 27.6m
Est. value
NOK 21.9m

Financial health · 2024

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

Who owns JULNES EIENDOM AS?

SUNNI JULNES
JULNES EIENDOM AS
NOK 2.1m rev. · NOK 965,000 profit

JULNES EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JULNES EIENDOM AS own?

JULNES EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JULNES EIENDOM AS

Who owns JULNES EIENDOM AS?

SUNNI JULNES is the largest registered owner, with 80.0%.

What is the revenue of JULNES EIENDOM AS?

JULNES EIENDOM AS had revenue of NOK 2.1m in 2024.

Who is the general manager of JULNES EIENDOM AS?

Knut Inge Julnes is registered as general manager of JULNES EIENDOM AS.

Where is JULNES EIENDOM AS based?

JULNES EIENDOM AS has its business address in Florø.

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.