BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

FISKEGULL AS

Org. no. 923365974 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 240,000
Operating profit NOK 182,000
Equity NOK 135,000
Incorporated 2019
Share capital NOK 100,000

FISKEGULL AS is registered as a limited company in Tønsberg, Vestfold with organisation number 923365974. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå produksjons-, handels og agenturvirksomhet, herunder eksport og import og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 240,000 in revenue and NOK 182,000 in operating profit.

Key figures · 2025

Revenue
NOK 240,000
Operating profit
NOK 182,000
Equity
NOK 135,000
Est. value
NOK 669,000

Financial health · 2025

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

Who owns FISKEGULL AS?

SEAFOODNORWAY AS
FISKEGULL AS
NOK 240,000 rev. · NOK 182,000 profit

FISKEGULL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FISKEGULL AS

Who owns FISKEGULL AS?

SEAFOODNORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of FISKEGULL AS?

FISKEGULL AS had revenue of NOK 240,000 in 2025.

Who is the general manager of FISKEGULL AS?

Hassan Hayat Rana is registered as general manager of FISKEGULL AS.

Where is FISKEGULL AS based?

FISKEGULL AS has its business address in Tolvsrød.

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.