BIZTRAC BETA
Development of building projects

GEILO INVEST AS

Org. no. 989896210 Limited company (AS) Hol Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −1.8m
Equity NOK 17.3m
Incorporated 2006
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,8 mill kr).

GEILO INVEST AS is registered as a limited company in Hol, Buskerud with organisation number 989896210. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2006. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Investering og utvikling av eiendom, håndverkertjenester samt relaterte tjenester til hytteeierne. Videre kan selskapet drive med generell omsetning av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −1.8m in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −1.8m
Equity
NOK 17.3m
Est. value
NOK 13.8m

Financial health · 2025

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

Who owns GEILO INVEST AS?

GUNNAR LEIF TRØEN
GEILO INVEST AS
NOK 1.3m rev. · NOK −1.8m profit

GEILO INVEST AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GEILO INVEST AS

Who owns GEILO INVEST AS?

GUNNAR LEIF TRØEN is the largest registered owner, with 30.0%.

What is the revenue of GEILO INVEST AS?

GEILO INVEST AS had revenue of NOK 1.3m in 2025.

Who is the general manager of GEILO INVEST AS?

Stig Søndrol Trøen is registered as general manager of GEILO INVEST AS.

Where is GEILO INVEST AS based?

GEILO INVEST AS has its business address in Ustaoset.

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.