BIZTRAC BETA
Other captive investment companies

GIL INVEST AS

Org. no. 989258761 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 1.0m
Equity NOK 29.7m
Incorporated 2005
Share capital NOK 200,000

GIL INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 989258761. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 1 shares. The company's stated purpose is: “Investere i børsnoterte og unoterte verdipapirer og finansielle instrumenter. Videre er formålet å levere rådgivning innenfor strategi og ledelse til virksomheter hvor Selskapet er investor samt til andre virksomheter der kompetanse og relasjoner kan skape varige verdier for både kunder og selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 1.0m
Equity
NOK 29.7m
Est. value
NOK 19.4m

Financial health · 2024

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

Who owns GIL INVEST AS?

GEIR INGE LUNDE
GIL INVEST AS
NOK 1.5m rev. · NOK 1.0m profit

GIL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GIL INVEST AS own?

GIL INVEST AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about GIL INVEST AS

Who owns GIL INVEST AS?

GEIR INGE LUNDE is the largest registered owner, with 100.0%.

What is the revenue of GIL INVEST AS?

GIL INVEST AS had revenue of NOK 1.5m in 2024.

Where is GIL INVEST AS based?

GIL INVEST AS has its business address in Paradis.

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.