BIZTRAC BETA
Development of building projects

SENTRUMSBOLIGER ALTA AS

Org. no. 819117152 Limited company (AS) Alta Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 2.6m

Signals

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

SENTRUMSBOLIGER ALTA AS is registered as a limited company in Alta, Finnmark with organisation number 819117152. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 2.6m, divided into 26000 shares. The company's stated purpose is: “Utvikling og salg av fast eiendom, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns SENTRUMSBOLIGER ALTA AS?

GISLE EIENDOM AS
SENTRUMSBOLIGER ALTA AS
NOK 0 rev. · NOK −38,000 profit

SENTRUMSBOLIGER ALTA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SENTRUMSBOLIGER ALTA AS own?

SENTRUMSBOLIGER ALTA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SENTRUMSBOLIGER ALTA AS

Who owns SENTRUMSBOLIGER ALTA AS?

GISLE EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of SENTRUMSBOLIGER ALTA AS?

SENTRUMSBOLIGER ALTA AS had revenue of NOK 0 in 2025.

Where is SENTRUMSBOLIGER ALTA AS based?

SENTRUMSBOLIGER ALTA AS has its business address in Alta.

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.