BIZTRAC BETA
Activities of excursion and event organisers

EPLERIET AS

Org. no. 926429191 Limited company (AS) Hjelmeland Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 64,000
Equity NOK 4.3m
Incorporated 2021
Employees 7
Share capital NOK 60,000

EPLERIET AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 926429191. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2021 and has 7 registered employees. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Turist destinasjon, selskapsarrangement, salg av varer i tilknytning til dette, samt eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 64,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 64,000
Equity
NOK 4.3m
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns EPLERIET AS?

KRISTEN HELGØY
EPLERIET AS
NOK 2.9m rev. · NOK 64,000 profit

EPLERIET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EPLERIET AS own?

EPLERIET AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EPLERIET AS

Who owns EPLERIET AS?

KRISTEN HELGØY is the largest registered owner, with 100.0%.

What is the revenue of EPLERIET AS?

EPLERIET AS had revenue of NOK 2.9m in 2025.

Who is the general manager of EPLERIET AS?

Anne Norunn Helgøy is registered as general manager of EPLERIET AS.

Where is EPLERIET AS based?

EPLERIET AS has its business address in Helgøy I Ryfylke.

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.