BIZTRAC BETA
Rental and operating of own or leased real estate

SENTRUM BREIVIKA AS

Org. no. 993455644 Limited company (AS) Surnadal Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 12.9m
Operating profit NOK 5.8m
Equity NOK 65.2m
Incorporated 2008
Share capital NOK 6.3m

Signals

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

SENTRUM BREIVIKA AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 993455644. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 6.3m, divided into 100 shares. The company's stated purpose is: “Utvikling, utleie og drift av fast eiendom samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.9m in revenue and NOK 5.8m in operating profit.

Key figures · 2024

Revenue
NOK 12.9m
Operating profit
NOK 5.8m
Equity
NOK 65.2m
Est. value
NOK 60.2m

Financial health · 2024

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

Who owns SENTRUM BREIVIKA AS?

AMFI AS
SENTRUM BREIVIKA AS
NOK 12.9m rev. · NOK 5.8m profit

SENTRUM BREIVIKA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SENTRUM BREIVIKA AS er morselskap for 65 datterselskaper:

Frequently asked questions about SENTRUM BREIVIKA AS

Who owns SENTRUM BREIVIKA AS?

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

What is the revenue of SENTRUM BREIVIKA AS?

SENTRUM BREIVIKA AS had revenue of NOK 12.9m in 2024.

Where is SENTRUM BREIVIKA AS based?

SENTRUM BREIVIKA 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.