BIZTRAC BETA
Restaurant activities

FAVN DRIFT AS

Org. no. 930272922 Limited company (AS) Bodø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 9.0m
Operating profit NOK 473,000
Equity NOK 58,000
Incorporated 2022
Employees 7
Share capital NOK 50,000

FAVN DRIFT AS is registered as a limited company in Bodø, Nordland with organisation number 930272922. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 7 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Drift av hovedkontor for konsernets serveringsvirksomhet. Selskapet kan gå inn med kapital/delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.0m in revenue and NOK 473,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.0m
Operating profit
NOK 473,000
Equity
NOK 58,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FAVN DRIFT AS?

TESA INVEST AS
FAVN DRIFT AS
NOK 9.0m rev. · NOK 473,000 profit

FAVN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FAVN DRIFT AS own?

FAVN DRIFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FAVN DRIFT AS

Who owns FAVN DRIFT AS?

TESA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of FAVN DRIFT AS?

FAVN DRIFT AS had revenue of NOK 9.0m in 2025.

Who is the general manager of FAVN DRIFT AS?

Rolf Fredrik Ekelund is registered as general manager of FAVN DRIFT AS.

Where is FAVN DRIFT AS based?

FAVN DRIFT AS has its business address in Bodø.

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.