BIZTRAC BETA
Logistics service activities

GISKE LOGISTICS AS

Org. no. 987101822 Limited company (AS) Ålesund Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 20.1m
Operating profit NOK −750,000
Equity NOK 109,000
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−750k kr).

GISKE LOGISTICS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 987101822. The business is classified under logistics service activities (NACE 52.250). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Spedisjons- og agenturvirksomhet innenfor sjøtransport, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.1m in revenue and NOK −750,000 in operating profit.

Key figures · 2024

Revenue
NOK 20.1m
Operating profit
NOK −750,000
Equity
NOK 109,000
Est. value
NOK 9.4m

Financial health · 2024

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

Who owns GISKE LOGISTICS AS?

GISKE GROUP COMPANY AS
GISKE LOGISTICS AS
NOK 20.1m rev. · NOK −750,000 profit

GISKE LOGISTICS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GISKE LOGISTICS AS

Who owns GISKE LOGISTICS AS?

GISKE GROUP COMPANY AS is the largest registered owner, with 100.0%.

What is the revenue of GISKE LOGISTICS AS?

GISKE LOGISTICS AS had revenue of NOK 20.1m in 2024.

Who is the general manager of GISKE LOGISTICS AS?

Steinar Hansi Giske is registered as general manager of GISKE LOGISTICS AS.

Where is GISKE LOGISTICS AS based?

GISKE LOGISTICS AS has its business address in Ålesund.

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.