biztrac. BETA
COMPANY REGISTER PROFILE
935967449 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

FET POTET AS

Org. no. 935967449 Limited company (AS) Askøy Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 70,000
Operating profit NOK 34,000
Equity NOK 52,000
Incorporated 2025
Share capital NOK 30,000

FET POTET AS is registered as a limited company in Askøy, Vestland with organisation number 935967449. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen gatekjøkkendrift - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 70,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 70,000
Operating profit
NOK 34,000
Equity
NOK 52,000
Est. value
NOK 129,000

Financial health · 2025

Liquidity
2.28
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
56.2%
Weak
Equity as a share of total capital

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

Who owns FET POTET AS?

FET POTET AS
NOK 70,000 rev. · NOK 34,000 profit

FET POTET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FET POTET AS

Who owns FET POTET AS?

Odin Varg Jørgensen is the largest registered owner, with 100.0%.

What is the revenue of FET POTET AS?

FET POTET AS had revenue of NOK 70,000 in 2025.

Who is the general manager of FET POTET AS?

Chutikan Petterson is registered as general manager of FET POTET AS.

Where is FET POTET AS based?

FET POTET AS has its business address in Strusshamn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.