biztrac. BETA
COMPANY REGISTER PROFILE
921975260 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

GESTU HOLDING AS

Org. no. 921975260 Limited company (AS) Grimstad Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 4.1m
Incorporated 2018
Share capital NOK 30,000

Signals

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

GESTU HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 921975260. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i eiendom og selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
▼ −3 %
Equity
NOK 4.1m
▲ +6 %
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
91.4%
Very good
Equity as a share of total capital

Who owns GESTU HOLDING AS?

GESTU HOLDING AS
NOK 0 rev. · NOK −9,000 profit

GESTU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GESTU HOLDING AS own?

GESTU HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GESTU HOLDING AS

Who owns GESTU HOLDING AS?

Geir Sture is the largest registered owner, with 100.0%.

What is the revenue of GESTU HOLDING AS?

GESTU HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of GESTU HOLDING AS?

Geir Sture is registered as general manager of GESTU HOLDING AS.

Where is GESTU HOLDING AS based?

GESTU HOLDING AS has its business address in Fevik.

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.