BIZTRAC BETA
Rental and operating of own or leased real estate

KOPPANGSENTERET AS

Org. no. 931315951 Limited company (AS) Surnadal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 1.1m
Equity NOK 32.0m
Incorporated 2022
Share capital NOK 586,000

Signals

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

KOPPANGSENTERET AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 931315951. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 586,000, divided into 23448 shares. The company's stated purpose is: “Kjøp, utvikling, drift, forvaltning og salg av fast eiendom, samt det som naturlig står i forhold til dette, herunder også deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 1.1m
Equity
NOK 32.0m
Est. value
NOK 24.6m

Financial health · 2024

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

Who owns KOPPANGSENTERET AS?

SETRA SURNADAL II AS
KOPPANGSENTERET AS
NOK 2.7m rev. · NOK 1.1m profit

KOPPANGSENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOPPANGSENTERET AS

Who owns KOPPANGSENTERET AS?

SETRA SURNADAL II AS is the largest registered owner, with 100.0%.

What is the revenue of KOPPANGSENTERET AS?

KOPPANGSENTERET AS had revenue of NOK 2.7m in 2024.

Where is KOPPANGSENTERET AS based?

KOPPANGSENTERET 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.