BIZTRAC BETA
COMPANY REGISTER PROFILE
986239340 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other unspecified social services without accommodation

GEILO RØDE KORS

Org. no. 986239340 Association/club/organisation (FLI) Hol Incorporated 1980 Active
Ownership graph ↗
Revenue 2023 NOK 1.5m
Operating profit NOK −186,000
Equity NOK 7.4m
Incorporated 1980

Signals

1 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−186k kr).

GEILO RØDE KORS is registered as a association/club/organisation in Hol, Buskerud with organisation number 986239340. The business is classified under other unspecified social services without accommodation (NACE 88.996). The company was incorporated in 1980. The most recent filed accounts, for the 2023 financial year, show NOK 1.5m in revenue and NOK −186,000 in operating profit.

Key figures · 2023

Revenue
NOK 1.5m
Operating profit
NOK −186,000
Equity
NOK 7.4m
Est. value
NOK 5.8m

Financial health · 2023

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

Who owns GEILO RØDE KORS?

No shareholders are registered for GEILO RØDE KORS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GEILO RØDE KORS

What is the revenue of GEILO RØDE KORS?

GEILO RØDE KORS had revenue of NOK 1.5m in 2023.

Where is GEILO RØDE KORS based?

GEILO RØDE KORS has its business address in Geilo.

Property

Business address Bakkestølvegen 56, 3580 Geilo
Cadastral unit 3330-66/453/0/0

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.