BIZTRAC BETA
Restaurant activities

FELLINI LOFOTEN AS

Org. no. 926037854 Limited company (AS) Vågan Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 17.3m
Operating profit NOK 1.9m
Equity NOK 2.7m
Incorporated 2020
Employees 26
Share capital NOK 30,000

FELLINI LOFOTEN AS is registered as a limited company in Vågan, Nordland with organisation number 926037854. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 26 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurant- og kafévirksomhet, samt annen aktivitet som faller naturlig sammen med dette, herunder engasjement i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.3m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 17.3m
Operating profit
NOK 1.9m
Equity
NOK 2.7m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns FELLINI LOFOTEN AS?

HORORIGÅRDEN AS
FELLINI LOFOTEN AS
NOK 17.3m rev. · NOK 1.9m profit

FELLINI LOFOTEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FELLINI LOFOTEN AS er morselskap for 1 datterselskap:

Frequently asked questions about FELLINI LOFOTEN AS

Who owns FELLINI LOFOTEN AS?

HORORIGÅRDEN AS is the largest registered owner, with 100.0%.

What is the revenue of FELLINI LOFOTEN AS?

FELLINI LOFOTEN AS had revenue of NOK 17.3m in 2024.

Who is the general manager of FELLINI LOFOTEN AS?

Welat Horori is registered as general manager of FELLINI LOFOTEN AS.

Where is FELLINI LOFOTEN AS based?

FELLINI LOFOTEN AS has its business address in Svolvær.

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.