BIZTRAC BETA
Retail sale of sports equipment

GEILO SPORT AS

Org. no. 911952157 Limited company (AS) Hol Incorporated 1934 Active
Ownership graph ↗
Revenue 2025 NOK 21.3m
Operating profit NOK −800,000
Equity NOK 10.7m
Incorporated 1934
Employees 15
Share capital NOK 320,000

Signals

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

GEILO SPORT AS is registered as a limited company in Hol, Buskerud with organisation number 911952157. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 1934 and has 15 registered employees. Registered share capital is NOK 320,000, divided into 421 shares. The company's stated purpose is: “Handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.3m in revenue and NOK −800,000 in operating profit.

Key figures · 2025

Revenue
NOK 21.3m
Operating profit
NOK −800,000
Equity
NOK 10.7m
Est. value
NOK 12.0m

Financial health · 2025

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

Who owns GEILO SPORT AS?

AUD HVAMMEN LUNDE
GEILO SPORT AS
NOK 21.3m rev. · NOK −800,000 profit

GEILO SPORT AS has 6 registered shareholders:

All shareholders and roles →

Which companies does GEILO SPORT AS own?

GEILO SPORT AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about GEILO SPORT AS

Who owns GEILO SPORT AS?

AUD HVAMMEN LUNDE is the largest registered owner, with 33.3%.

What is the revenue of GEILO SPORT AS?

GEILO SPORT AS had revenue of NOK 21.3m in 2025.

Who is the general manager of GEILO SPORT AS?

Vilde Videsjorden Bakkeplass is registered as general manager of GEILO SPORT AS.

Where is GEILO SPORT AS based?

GEILO SPORT AS has its business address in Geilo.

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.