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

DICKAUNSVINGEN 21/23 AS

Org. no. 914350506 Limited company (AS) Trondheim Incorporated 2014 Active
Operating profit NOK −35,000
Equity NOK 70,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

DICKAUNSVINGEN 21/23 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914350506. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å drive generell investeringsvirksomhet, herunder å investere i andre selskap.”.

Former names: PIONER AKTIVT EIERSKAP AEGA AS, HAAKON VII'S GATE 15/17 HOLDING AS

Key figures · 2025

Operating profit
NOK −35,000
▼ −101 %
Equity
NOK 70,000
▼ −4 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
5.72
Very good
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
12.6%
Weak
Equity as a share of total capital

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

Who owns DICKAUNSVINGEN 21/23 AS?

DICKAUNSVINGEN 21/23 AS
· NOK −35,000 profit

DICKAUNSVINGEN 21/23 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DICKAUNSVINGEN 21/23 AS

Who owns DICKAUNSVINGEN 21/23 AS?

GH HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of DICKAUNSVINGEN 21/23 AS?

Jan Gunnar Heglund is registered as general manager of DICKAUNSVINGEN 21/23 AS.

Where is DICKAUNSVINGEN 21/23 AS based?

DICKAUNSVINGEN 21/23 AS 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.