biztrac. BETA
COMPANY REGISTER PROFILE
999277705 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

DNB KONTOR AS

Org. no. 999277705 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 3.1bn
Incorporated 2012
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DNB KONTOR AS is registered as a limited company in Bergen, Vestland with organisation number 999277705. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 300,000, divided into 1 shares. The company's stated purpose is: “Selskapets formål er å eie og forvalte eiendomsselskaper og det som naturlig hører til.”.

Key figures · 2025

Operating profit
NOK −6,000
▲ +63 %
Equity
NOK 3.1bn
▲ +0 %
Est. value
NOK 3.4bn

Financial health · 2025

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
4.7%
Weak
Return on total assets
Solidity
89.5%
Very good
Equity as a share of total capital

Who owns DNB KONTOR AS?

DNB KONTOR AS
· NOK −6,000 profit

DNB KONTOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DNB KONTOR AS own?

DNB KONTOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DNB KONTOR AS

Who owns DNB KONTOR AS?

DNB LIVSFORSIKRING AS is the largest registered owner, with 100.0%.

Who is the general manager of DNB KONTOR AS?

Gro Kristin Boge is registered as general manager of DNB KONTOR AS.

Where is DNB KONTOR AS based?

DNB KONTOR AS has its business address in Bergen.

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.