BIZTRAC BETA
COMPANY REGISTER PROFILE
837889812 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Other monetary intermediation

SKUE SPAREBANK

Org. no. 837889812 Savings bank (SPA) Hol Listed SKUE Incorporated 1842 Active
Ownership graph ↗
Incorporated 1842
Employees 148
Share capital NOK 173.4m

SKUE SPAREBANK is registered as a savings bank in Hol, Buskerud with organisation number 837889812. The business is classified under other monetary intermediation (NACE 64.190). The company was incorporated in 1842 and has 148 registered employees. Registered share capital is NOK 173.4m. The company's stated purpose is: “Utføre forretninger og tjenester som det er vanlig eller naturlig at sparebanker kan utføre i henhold til den til enhver tid gjeldende lovgivning og de til enhver tid gitte konsesjoner.”.

Former names: NES PRESTEGJELDS SPAREBANK

Who owns SKUE SPAREBANK?

SKUE SPAREBANK has 20+ registered shareholders:

All shareholders and roles →

Which companies does SKUE SPAREBANK own?

SKUE SPAREBANK holds stakes in 20 companies:

See the full ownership structure →

Frequently asked questions about SKUE SPAREBANK

Who owns SKUE SPAREBANK?

SPAREBANKSTIFTELSEN SKUE SPAREBANK is the largest registered owner, with 12.8%.

Who is the general manager of SKUE SPAREBANK?

Hans Kristian Glesne is registered as general manager of SKUE SPAREBANK.

Where is SKUE SPAREBANK based?

SKUE SPAREBANK has its business address in Geilo.

Property

Business address Geilovegen 34, 3580 Geilo
Cadastral unit 3330-64/202/0/0
Building Kontor- og administrasjonsbygning, rådhus · 6 units

2 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.