biztrac. BETA
COMPANY REGISTER PROFILE
937901003 ORG. NO. 2025 ACCOUNTS 12 SECTIONS
Active UPDATED 03.10.2026
Other monetary intermediation

SPAREBANK 1 SMN

Org. no. 937901003 Savings bank (SPA) Trondheim Listed MING Incorporated 1823 Active
Ownership graph ↗
Incorporated 1823
Employees 929
Share capital NOK 2.9bn

SPAREBANK 1 SMN is registered as a savings bank in Trondheim, Trøndelag with organisation number 937901003. The business is classified under other monetary intermediation (NACE 64.190). The company was incorporated in 1823 and has 929 registered employees. Registered share capital is NOK 2.9bn. The company's stated purpose is: “Drive virksomhet som bank og for øvrig drive og delta i virksomhet som sparebanken kan utføre i henhold til tillatelser og den til enhver tid gjeldende lovgivning.”.

Former names: Sparebanken Midt-Norge

Who owns SPAREBANK 1 SMN?

J.P. MORGAN SE 12 accounts
STATE STREET BANK AND TRUST COMP 14 accounts
JPMORGAN CHASE BANK, N.A., LONDON 11 accounts
SKANDINAVISKA ENSKILDA BANKEN AB 10 accounts
THE NORTHERN TRUST COMP, LONDON BR 12 accounts
THE BANK OF NEW YORK MELLON 23 accounts
CITIBANK, N.A. IE
THE BANK OF NEW YORK MELLON SA/NV 12 accounts
BROWN BROTHERS HARRIMAN & CO. 12 accounts
SPAREBANK 1 SMN

SPAREBANK 1 SMN has 20+ registered shareholders:

All shareholders and roles →

Which companies does SPAREBANK 1 SMN own?

SPAREBANK 1 SMN holds stakes in 38 companies:

See the full ownership structure →

Group structure

SPAREBANK 1 SMN er morselskap for 12 datterselskaper:

Frequently asked questions about SPAREBANK 1 SMN

Who owns SPAREBANK 1 SMN?

SPAREBANKSTIFTINGA SØRE SUNNMØRE is the largest registered owner, with 7.3%.

Who is the general manager of SPAREBANK 1 SMN?

Jan-Frode Janson is registered as general manager of SPAREBANK 1 SMN.

Where is SPAREBANK 1 SMN based?

SPAREBANK 1 SMN has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.