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

ÅSANE STORSENTER DA

Org. no. 857187342 General partnership with shared liability (DA) Bergen Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 156.4m
Operating profit NOK 46.1m
Equity NOK 1.9bn
Incorporated 1990
Employees 19

ÅSANE STORSENTER DA is registered as a general partnership with shared liability in Bergen, Vestland with organisation number 857187342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990 and has 19 registered employees. The company's stated purpose is: “Investering i, og forvaltning og utvikling av, fast eiendom, herunder deltagelse i andre selskaper og alt som står i forbindelse med det.”. The most recent filed accounts, for the 2025 financial year, show NOK 156.4m in revenue and NOK 46.1m in operating profit.

Former names: ANS ARKEN

Key figures · 2025

Revenue
NOK 156.4m
▲ +8 %
Operating profit
NOK 46.1m
▼ −10 %
Equity
NOK 1.9bn
▲ +4 %
Est. value
NOK 1.5bn

Financial health · 2025

Liquidity
14.44
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
97.7%
Very good
Equity as a share of total capital

Who owns ÅSANE STORSENTER DA?

No shareholders are registered for ÅSANE STORSENTER DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does ÅSANE STORSENTER DA own?

ÅSANE STORSENTER DA holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ÅSANE STORSENTER DA

What is the revenue of ÅSANE STORSENTER DA?

ÅSANE STORSENTER DA had revenue of NOK 156.4m in 2025.

Where is ÅSANE STORSENTER DA based?

ÅSANE STORSENTER DA has its business address in Ulset.

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.