BIZTRAC BETA
COMPANY REGISTER PROFILE
915388728 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

GESTIMA AS

Org. no. 915388728 Limited company (AS) Stad Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −37,000
Equity NOK 2.7m
Incorporated 2015
Share capital NOK 713,000

Signals

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

GESTIMA AS is registered as a limited company in Stad, Vestland with organisation number 915388728. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 713,000, divided into 71250 shares. The company's stated purpose is: “Kjøp, sal og forvaltning av aksjar og dessutan utøve dei funksjonane som normalt ligg under rolla som holdingselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −37,000
▲ +27 %
Equity
NOK 2.7m
▲ +6 %
Est. value
NOK 5.4m

Financial health · 2025

Liquidity
3.51
Very good
Current assets ÷ current liabilities
Profitability
27.3%
Very good
Return on total assets
Solidity
77.4%
Very good
Equity as a share of total capital

Who owns GESTIMA AS?

GESTIMA AS
NOK 0 rev. · NOK −37,000 profit

GESTIMA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GESTIMA AS own?

GESTIMA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GESTIMA AS

Who owns GESTIMA AS?

JARLE SKÅRHAUG is the largest registered owner, with 100.0%.

What is the revenue of GESTIMA AS?

GESTIMA AS had revenue of NOK 0 in 2025.

Where is GESTIMA AS based?

GESTIMA AS has its business address in Nordfjordeid.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.