BIZTRAC BETA
Holiday and other short-stay accommodation

JERGUL EIENDOM AS

Org. no. 976148150 Limited company (AS) Karasjok Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 546,000
Operating profit NOK 29,000
Equity NOK 2.5m
Incorporated 1996
Share capital NOK 1.2m

JERGUL EIENDOM AS is registered as a limited company in Karasjok, Finnmark with organisation number 976148150. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 1996. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Utleie av reiselivsanlegg, samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 546,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2024

Revenue
NOK 546,000
Operating profit
NOK 29,000
Equity
NOK 2.5m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns JERGUL EIENDOM AS?

JENS ÅGE HOLMESTRAND
JERGUL EIENDOM AS
NOK 546,000 rev. · NOK 29,000 profit

JERGUL EIENDOM AS has 11 registered shareholders:

All shareholders and roles →

Which companies does JERGUL EIENDOM AS own?

JERGUL EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JERGUL EIENDOM AS

Who owns JERGUL EIENDOM AS?

JENS ÅGE HOLMESTRAND is the largest registered owner, with 14.0%.

What is the revenue of JERGUL EIENDOM AS?

JERGUL EIENDOM AS had revenue of NOK 546,000 in 2024.

Who is the general manager of JERGUL EIENDOM AS?

Hans Arild Holmestrand is registered as general manager of JERGUL EIENDOM AS.

Where is JERGUL EIENDOM AS based?

JERGUL EIENDOM AS has its business address in Karasjok.

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.