BIZTRAC BETA
Camping grounds and recreational vehicle parks

JULE FERIE OG FRITID AS

Org. no. 975383962 Limited company (AS) Lierne Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 100,000
Operating profit NOK 35,000
Equity NOK 443,000
Incorporated 1995
Share capital NOK 224,000

JULE FERIE OG FRITID AS is registered as a limited company in Lierne, Trøndelag with organisation number 975383962. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 1995. Registered share capital is NOK 224,000. The company's stated purpose is: “Overnatting, hytteutleie, ferie- og fritids- aktiviteter samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 100,000 in revenue and NOK 35,000 in operating profit.

Key figures · 2025

Revenue
NOK 100,000
Operating profit
NOK 35,000
Equity
NOK 443,000
Est. value
NOK 355,000

Financial health · 2025

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

Who owns JULE FERIE OG FRITID AS?

PER BIRGER NESS
JULE FERIE OG FRITID AS
NOK 100,000 rev. · NOK 35,000 profit

JULE FERIE OG FRITID AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about JULE FERIE OG FRITID AS

Who owns JULE FERIE OG FRITID AS?

PER BIRGER NESS is the largest registered owner, with 22.3%.

What is the revenue of JULE FERIE OG FRITID AS?

JULE FERIE OG FRITID AS had revenue of NOK 100,000 in 2025.

Who is the general manager of JULE FERIE OG FRITID AS?

Bjørg Oliv Krystad Inderdal is registered as general manager of JULE FERIE OG FRITID AS.

Where is JULE FERIE OG FRITID AS based?

JULE FERIE OG FRITID AS has its business address in Sørli.

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.