BIZTRAC BETA
Support activities for fishing and aquaculture

GIAFA INDUSTRIER AS

Org. no. 915692273 Limited company (AS) Lillestrøm Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 86,000
Equity NOK 57.4m
Incorporated 2015
Share capital NOK 200,000

GIAFA INDUSTRIER AS is registered as a limited company in Lillestrøm, Akershus with organisation number 915692273. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2015. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Investering i andre selskaper, andre investeringer og tilhørende virksomhet, samt levere konsulentoppdrag og andre tjenester som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 86,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 86,000
Equity
NOK 57.4m
Est. value
NOK 28.8m

Financial health · 2024

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

Who owns GIAFA INDUSTRIER AS?

GØRILL SLOTTERØY LORENTSEN
GIAFA INDUSTRIER AS
NOK 4.7m rev. · NOK 86,000 profit

GIAFA INDUSTRIER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GIAFA INDUSTRIER AS own?

GIAFA INDUSTRIER AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GIAFA INDUSTRIER AS

Who owns GIAFA INDUSTRIER AS?

GØRILL SLOTTERØY LORENTSEN is the largest registered owner, with 50.0%.

What is the revenue of GIAFA INDUSTRIER AS?

GIAFA INDUSTRIER AS had revenue of NOK 4.7m in 2024.

Where is GIAFA INDUSTRIER AS based?

GIAFA INDUSTRIER AS has its business address in Lillestrøm.

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.