biztrac. BETA
COMPANY REGISTER PROFILE
919383739 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

GISKE ANLEGG HOLDING AS

Org. no. 919383739 Limited company (AS) Giske Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 2.2m
Incorporated 2017
Share capital NOK 2.5m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

GISKE ANLEGG HOLDING AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 919383739. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 2.5m, divided into 245000 shares. The company's stated purpose is: “Virksomhet innen maskin entreprenør bransjen. Herunder å eie andeler og aksjer i andre selskap.”.

Key figures · 2025

Operating profit
NOK −28,000
▼ −3 %
Equity
NOK 2.2m
▼ −1 %
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
91.8%
Very good
Equity as a share of total capital

Who owns GISKE ANLEGG HOLDING AS?

GISKE ANLEGG HOLDING AS has 6 registered shareholders:

All shareholders and roles →

Which companies does GISKE ANLEGG HOLDING AS own?

GISKE ANLEGG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

GISKE ANLEGG HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about GISKE ANLEGG HOLDING AS

Who owns GISKE ANLEGG HOLDING AS?

Kjetil Olav Godø Furnes is the largest registered owner, with 19.4%.

Who is the general manager of GISKE ANLEGG HOLDING AS?

Mats Ludvig Furnes is registered as general manager of GISKE ANLEGG HOLDING AS.

Where is GISKE ANLEGG HOLDING AS based?

GISKE ANLEGG HOLDING AS has its business address in Valderøya.

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.