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

ROALD AMUNDSENSGT 6 HJEMMEL AS

Org. no. 984070039 Limited company (AS) Bergen Incorporated 2001 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2001
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ROALD AMUNDSENSGT 6 HJEMMEL AS is registered as a limited company in Bergen, Vestland with organisation number 984070039. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Selskapets virksomhet er knyttet til fast eiendom og det som er naturlig hører til slik virksomhet, dog innenfor rammen av DnB NOR-gruppens virksomhet.”.

Former names: ROALD AMUNDSENSGT 6 AS

Key figures · 2025

Equity
NOK 30,000
▲ +0 %
Est. value
NOK 27,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ROALD AMUNDSENSGT 6 HJEMMEL AS?

ROALD AMUNDSENSGT 6 HJEMMEL AS

ROALD AMUNDSENSGT 6 HJEMMEL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ROALD AMUNDSENSGT 6 HJEMMEL AS er morselskap for 14 datterselskaper:

Frequently asked questions about ROALD AMUNDSENSGT 6 HJEMMEL AS

Who owns ROALD AMUNDSENSGT 6 HJEMMEL AS?

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

Where is ROALD AMUNDSENSGT 6 HJEMMEL AS based?

ROALD AMUNDSENSGT 6 HJEMMEL 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.