BIZTRAC BETA
Rental and operating of own or leased real estate

KLOSTERGATA EIENDOMSUTVIKLING AS

Org. no. 960650042 Limited company (AS) Moss Incorporated 1991 Active
Ownership graph ↗
Operating profit NOK −27,000
Equity NOK 1.7m
Incorporated 1991
Share capital NOK 100,000

Signals

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

KLOSTERGATA EIENDOMSUTVIKLING AS is registered as a limited company in Moss, Østfold with organisation number 960650042. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Foreta investeringer fast eiendom, herunder kjøp, salg, utvikling, utleie, drift og forvaltning, samt å foreta investeringer i aksjer og andeler i selskaper med lignende virksomhet, herunder å være morselskap.”.

Key figures · 2024

Operating profit
NOK −27,000
Equity
NOK 1.7m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns KLOSTERGATA EIENDOMSUTVIKLING AS?

CENTRUM EIENDOM ØSTFOLD AS
KLOSTERGATA EIENDOMSUTVIKLING AS
· NOK −27,000 profit

KLOSTERGATA EIENDOMSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLOSTERGATA EIENDOMSUTVIKLING AS

Who owns KLOSTERGATA EIENDOMSUTVIKLING AS?

CENTRUM EIENDOM ØSTFOLD AS is the largest registered owner, with 100.0%.

Who is the general manager of KLOSTERGATA EIENDOMSUTVIKLING AS?

Hilde Omre is registered as general manager of KLOSTERGATA EIENDOMSUTVIKLING AS.

Where is KLOSTERGATA EIENDOMSUTVIKLING AS based?

KLOSTERGATA EIENDOMSUTVIKLING AS has its business address in Moss.

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.