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

DNB BOLIGKREDITT AS

Org. no. 985621551 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Incorporated 2003
Share capital NOK 4.5bn

DNB BOLIGKREDITT AS is registered as a limited company in Oslo, Oslo with organisation number 985621551. The business is classified under other monetary intermediation (NACE 64.190). The company was incorporated in 2003. Registered share capital is NOK 4.5bn, divided into 1 shares. The company's stated purpose is: “Yte og erverve bolighypoteklån, lån med pant i fritidseiendommer og fellessfinansiering av borettslag, som hovedsakelig finansieres ved opptak av obligasjonslån ved utstedelse av obligasjoner med fortrinnsrett.”.

Former names: DNB NOR BOLIGKREDITT AS

Who owns DNB BOLIGKREDITT AS?

DNB BOLIGKREDITT AS

DNB BOLIGKREDITT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DNB BOLIGKREDITT AS er morselskap for 14 datterselskaper:

Frequently asked questions about DNB BOLIGKREDITT AS

Who owns DNB BOLIGKREDITT AS?

DNB BANK ASA is the largest registered owner, with 100.0%.

Who is the general manager of DNB BOLIGKREDITT AS?

Hans Olav Rønningen is registered as general manager of DNB BOLIGKREDITT AS.

Where is DNB BOLIGKREDITT AS based?

DNB BOLIGKREDITT AS has its business address in Oslo.

Property

Business address Dronning Eufemias gate 30, 0191 Oslo
Cadastral unit 301-234/88/0/0
Building Kontor- og administrasjonsbygning, rådhus · 5 units

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