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

INSTABANK ASA

Org. no. 816914582 Public limited company (ASA) Oslo Listed INSTA Incorporated 2016 Active
Ownership graph ↗
Incorporated 2016
Employees 78
Share capital NOK 464.8m

Signals

1 flags
  • Nylig endring 2026-08-21 Aksjekapital registrert 2026-08-21.

INSTABANK ASA is registered as a public limited company in Oslo, Oslo with organisation number 816914582. The business is classified under other monetary intermediation (NACE 64.190). The company was incorporated in 2016 and has 78 registered employees. Registered share capital is NOK 464.8m, divided into 464819739 shares. The company's stated purpose is: “Banken kan innenfor rammen av 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: ACE PROSJEKT ASA

Who owns INSTABANK ASA?

INSTABANK ASA has 20+ registered shareholders:

All shareholders and roles →

Which companies does INSTABANK ASA own?

INSTABANK ASA holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INSTABANK ASA

Who owns INSTABANK ASA?

KISTEFOS AS is the largest registered owner, with 24.4%.

Who is the general manager of INSTABANK ASA?

Robert Berg is registered as general manager of INSTABANK ASA.

Where is INSTABANK ASA based?

INSTABANK ASA has its business address in Oslo.

Property

Business address Drammensveien 175, 0277 Oslo
Cadastral unit 301-5/1/0/0
Building Kontor- og administrasjonsbygning, rådhus · 3 units

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.