BIZTRAC BETA
Camping grounds and recreational vehicle parks

SAGENESET FERIESENTER AS

Org. no. 960164830 Limited company (AS) Sirdal Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 717,000
Equity NOK 8.5m
Incorporated 1991
Share capital NOK 300,000

SAGENESET FERIESENTER AS is registered as a limited company in Sirdal, Agder with organisation number 960164830. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 1991. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Utbygging og drift av turistsenter, samt hva hermed står i forbindelse. Selskapet kan delta i andre selskaper med lignende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 717,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 717,000
Equity
NOK 8.5m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns SAGENESET FERIESENTER AS?

EIANE HOLDING AS
SAGENESET FERIESENTER AS
NOK 3.2m rev. · NOK 717,000 profit

SAGENESET FERIESENTER AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAGENESET FERIESENTER AS

Who owns SAGENESET FERIESENTER AS?

EIANE HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of SAGENESET FERIESENTER AS?

SAGENESET FERIESENTER AS had revenue of NOK 3.2m in 2025.

Who is the general manager of SAGENESET FERIESENTER AS?

Johan Eiane is registered as general manager of SAGENESET FERIESENTER AS.

Where is SAGENESET FERIESENTER AS based?

SAGENESET FERIESENTER AS has its business address in Tjørhom.

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.