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

KREDITTBANKEN ASA

Org. no. 975966453 Public limited company (ASA) Trondheim Incorporated 1995 Active
Ownership graph ↗
Incorporated 1995
Employees 116
Share capital NOK 911.7m

KREDITTBANKEN ASA is registered as a public limited company in Trondheim, Trøndelag with organisation number 975966453. The business is classified under other monetary intermediation (NACE 64.190). The company was incorporated in 1995 and has 116 registered employees. Registered share capital is NOK 911.7m, divided into 9116998 shares. The company's stated purpose is: “Selskapet kan innenfor rammen av den gitte konsesjon og den lovgivning som til enhver tid gjelder, utføre alle forretninger og tjenester som det er vanlig eller naturlig at banker utfører.”.

Former names: SPAREBANKUTVIKLING AS, SPAREBANK 1 KREDITTKORT AS, SPAREBANK 1 KREDITT AS, SPAREBANK 1 KREDITT ASA

Who owns KREDITTBANKEN ASA?

KREDITTBANKEN ASA has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about KREDITTBANKEN ASA

Who owns KREDITTBANKEN ASA?

SPAREBANK 1 SØR-NORGE ASA is the largest registered owner, with 23.3%.

Who is the general manager of KREDITTBANKEN ASA?

Terje Gromholt is registered as general manager of KREDITTBANKEN ASA.

Where is KREDITTBANKEN ASA based?

KREDITTBANKEN ASA has its business address in Trondheim.

Property

Business address Søndre gate 4, 7011 Trondheim
Cadastral unit 5001-401/338/0/0
Building Annen kontorbygning · 3 units

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