BIZTRAC BETA
Uoppgitt

GIMMESTAD SANDE HOLDING AS

Org. no. 920125093 Limited company (AS) Øygarden Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −70,000
Equity NOK 4.1m
Incorporated 2017
Share capital NOK 60,000

Signals

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

GIMMESTAD SANDE HOLDING AS is registered as a limited company in Øygarden, Vestland with organisation number 920125093. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskap og det som naturlig hører til dette. Herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −70,000
Equity
NOK 4.1m
Est. value
NOK 8.9m

Financial health · 2024

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

Who owns GIMMESTAD SANDE HOLDING AS?

FREDRICK GIMMESTAD SANDE
GIMMESTAD SANDE HOLDING AS
· NOK −70,000 profit

GIMMESTAD SANDE HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GIMMESTAD SANDE HOLDING AS own?

GIMMESTAD SANDE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GIMMESTAD SANDE HOLDING AS

Who owns GIMMESTAD SANDE HOLDING AS?

FREDRICK GIMMESTAD SANDE is the largest registered owner, with 50.0%.

Who is the general manager of GIMMESTAD SANDE HOLDING AS?

Fredrick Gimmestad Sande is registered as general manager of GIMMESTAD SANDE HOLDING AS.

Where is GIMMESTAD SANDE HOLDING AS based?

GIMMESTAD SANDE HOLDING AS has its business address in Ågotnes.

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.