BIZTRAC BETA
Retail sale of other food

FØL DEG VEL AS

Org. no. 898907902 Limited company (AS) Stavanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 159,000
Equity NOK 341,000
Incorporated 2012
Employees 6
Share capital NOK 30,000

FØL DEG VEL AS is registered as a limited company in Stavanger, Rogaland with organisation number 898907902. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2012 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av helsekost og kosttilskudd og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK 159,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK 159,000
Equity
NOK 341,000
Est. value
NOK 790,000

Financial health · 2024

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

Who owns FØL DEG VEL AS?

SORAYA MORTAZAVY
FØL DEG VEL AS
NOK 5.1m rev. · NOK 159,000 profit

FØL DEG VEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FØL DEG VEL AS

Who owns FØL DEG VEL AS?

SORAYA MORTAZAVY is the largest registered owner, with 100.0%.

What is the revenue of FØL DEG VEL AS?

FØL DEG VEL AS had revenue of NOK 5.1m in 2025.

Who is the general manager of FØL DEG VEL AS?

Soraya Mortazavy is registered as general manager of FØL DEG VEL AS.

Where is FØL DEG VEL AS based?

FØL DEG VEL AS has its business address in Stavanger.

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.