BIZTRAC BETA
COMPANY REGISTER PROFILE
932481367 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

DENSKO INVEST AS

Org. no. 932481367 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

DENSKO INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 932481367. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av eiendom, herunder utleie. Drift av restaurant/gatekjøkken.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 24,000
▲ +0 %
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns DENSKO INVEST AS?

DENSKO INVEST AS
· NOK 0 profit

DENSKO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DENSKO INVEST AS own?

DENSKO INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DENSKO INVEST AS

Who owns DENSKO INVEST AS?

DENNIS SKORPEN is the largest registered owner, with 100.0%.

Where is DENSKO INVEST AS based?

DENSKO INVEST AS has its business address in Bergen.

Property

Business address Løbergstien 14, 5073 Bergen
Cadastral unit 4601-18/165/0/0
Building Enebolig · 1 unit

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.