BIZTRAC BETA
COMPANY REGISTER PROFILE
994039008 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

GIKS EIENDOM AS

Org. no. 994039008 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 320,000
Incorporated 2009
Share capital NOK 945,000

Signals

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

GIKS EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 994039008. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2009. Registered share capital is NOK 945,000, divided into 100 shares. The company's stated purpose is: “Investeringer i eiendom og andre selskaper og hva som herunder faller naturlig.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 320,000
Est. value
NOK 292,000

Financial health · 2025

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

Who owns GIKS EIENDOM AS?

GIKS EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GIKS EIENDOM AS

Who owns GIKS EIENDOM AS?

HUGO ARE NYLUND is the largest registered owner, with 25.0%.

Where is GIKS EIENDOM AS based?

GIKS EIENDOM AS has its business address in Nesttun.

Property

Business address Midtunhaugen 80, 5224 Nesttun
Cadastral unit 4601-43/95/0/0
Building Tomannsbolig, horisontaldelt · 2 units

5 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.