BIZTRAC BETA
Rental and operating of own or leased real estate

SKI SENTRUMSBYGG AS

Org. no. 913979494 Limited company (AS) Ås Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 11.9m
Operating profit NOK 9.3m
Equity NOK 18.3m
Incorporated 2014
Share capital NOK 3.6m

SKI SENTRUMSBYGG AS is registered as a limited company in Ås, Akershus with organisation number 913979494. 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 3.6m, divided into 1000000 shares. The company's stated purpose is: “Utleie og drift av fast eiendom, herunder å anskaffe, utvikle, forvalte og selge fast eiendom og alt som er beslektet eller står i forbindelse med slik virksomhet, direkte og/eller indirekte.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.9m in revenue and NOK 9.3m in operating profit.

Key figures · 2024

Revenue
NOK 11.9m
Operating profit
NOK 9.3m
Equity
NOK 18.3m
Est. value
NOK 23.0m

Financial health · 2024

Liquidity
9.12
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.5%
Satisfactory
Equity as a share of total capital

Who owns SKI SENTRUMSBYGG AS?

ANDRESEN AS
SKI SENTRUMSBYGG AS
NOK 11.9m rev. · NOK 9.3m profit

SKI SENTRUMSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKI SENTRUMSBYGG AS own?

SKI SENTRUMSBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKI SENTRUMSBYGG AS

Who owns SKI SENTRUMSBYGG AS?

ANDRESEN AS is the largest registered owner, with 100.0%.

What is the revenue of SKI SENTRUMSBYGG AS?

SKI SENTRUMSBYGG AS had revenue of NOK 11.9m in 2024.

Where is SKI SENTRUMSBYGG AS based?

SKI SENTRUMSBYGG AS has its business address in Ski.

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.