BIZTRAC BETA
Rental and operating of own or leased real estate

GULSKOGEN SENTER AS

Org. no. 917427593 Limited company (AS) Surnadal Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 163.3m
Operating profit NOK 110.4m
Equity NOK 982.2m
Incorporated 2016
Share capital NOK 10.0m

Signals

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

GULSKOGEN SENTER AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 917427593. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Å erverve fast eiendom for utvikling, utleie og hva hermed står i forbindelse, samt delta i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 163.3m in revenue and NOK 110.4m in operating profit.

Key figures · 2024

Revenue
NOK 163.3m
Operating profit
NOK 110.4m
Equity
NOK 982.2m
Est. value
NOK 851.2m

Financial health · 2024

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.8%
Very good
Equity as a share of total capital

Who owns GULSKOGEN SENTER AS?

AURORA EIENDOM AS
GULSKOGEN SENTER AS
NOK 163.3m rev. · NOK 110.4m profit

GULSKOGEN SENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULSKOGEN SENTER AS

Who owns GULSKOGEN SENTER AS?

AURORA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GULSKOGEN SENTER AS?

GULSKOGEN SENTER AS had revenue of NOK 163.3m in 2024.

Where is GULSKOGEN SENTER AS based?

GULSKOGEN SENTER AS has its business address in Surnadal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.