BIZTRAC BETA
Hotels and similar accommodation

FUGL FØNIX ETNE AS

Org. no. 989144944 Limited company (AS) Etne Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 16.1m
Operating profit NOK 3.9m
Equity NOK 3.3m
Incorporated 2005
Employees 21
Share capital NOK 100,000

FUGL FØNIX ETNE AS is registered as a limited company in Etne, Vestland with organisation number 989144944. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2005 and has 21 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Hotellvirksomhet eller annen aktivitet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.1m in revenue and NOK 3.9m in operating profit.

Key figures · 2024

Revenue
NOK 16.1m
Operating profit
NOK 3.9m
Equity
NOK 3.3m
Est. value
NOK 12.8m

Financial health · 2024

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.5%
Good
Equity as a share of total capital

Who owns FUGL FØNIX ETNE AS?

FUGL FØNIX AS
FUGL FØNIX ETNE AS
NOK 16.1m rev. · NOK 3.9m profit

FUGL FØNIX ETNE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FUGL FØNIX ETNE AS own?

FUGL FØNIX ETNE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FUGL FØNIX ETNE AS

Who owns FUGL FØNIX ETNE AS?

FUGL FØNIX AS is the largest registered owner, with 100.0%.

What is the revenue of FUGL FØNIX ETNE AS?

FUGL FØNIX ETNE AS had revenue of NOK 16.1m in 2024.

Who is the general manager of FUGL FØNIX ETNE AS?

Audun Stene is registered as general manager of FUGL FØNIX ETNE AS.

Where is FUGL FØNIX ETNE AS based?

FUGL FØNIX ETNE AS has its business address in Etne.

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.