BIZTRAC BETA
Buying and selling of own real estate

COOP EIENDOM ROGALAND AS

Org. no. 916047967 Limited company (AS) Klepp Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −137,000
Equity NOK 48.1m
Incorporated 2015
Share capital NOK 2.9m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−137k kr).

COOP EIENDOM ROGALAND AS is registered as a limited company in Klepp, Rogaland with organisation number 916047967. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 2.9m, divided into 2900 shares. The company's stated purpose is: “Å kjøpe, selge, utvikle og forvalte eiendommer/tomtearealer, samt utleie av lokaler og dertil hørende virksomhet.”.

Key figures · 2024

Operating profit
NOK −137,000
Equity
NOK 48.1m
Est. value
NOK 45.0m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.0%
Good
Equity as a share of total capital

Who owns COOP EIENDOM ROGALAND AS?

MADLA HANDELSLAG SA
COOP EIENDOM ROGALAND AS
· NOK −137,000 profit

COOP EIENDOM ROGALAND AS has 5 registered shareholders:

All shareholders and roles →

Which companies does COOP EIENDOM ROGALAND AS own?

COOP EIENDOM ROGALAND AS holds a stake in 1 company:

See the full ownership structure →

Group structure

COOP EIENDOM ROGALAND AS er morselskap for 1 datterselskap:

Frequently asked questions about COOP EIENDOM ROGALAND AS

Who owns COOP EIENDOM ROGALAND AS?

MADLA HANDELSLAG SA is the largest registered owner, with 20.0%.

Who is the general manager of COOP EIENDOM ROGALAND AS?

Frank Skjæveland is registered as general manager of COOP EIENDOM ROGALAND AS.

Where is COOP EIENDOM ROGALAND AS based?

COOP EIENDOM ROGALAND AS has its business address in Klepp Stasjon.

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.