biztrac. BETA
COMPANY REGISTER PROFILE
995247496 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

EIENDOMSSELSKAPET CORSO RUGGERO

Org. no. 995247496 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −85,000
Equity NOK −263,000
Incorporated 2010
Share capital NOK 150,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−262k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−85k kr).

EIENDOMSSELSKAPET CORSO RUGGERO is registered as a limited company in Oslo, Oslo with organisation number 995247496. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Eie og leie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −85,000
▲ +0 %
Equity
NOK −263,000
▲ +0 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-66624.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EIENDOMSSELSKAPET CORSO RUGGERO?

EIENDOMSSELSKAPET CORSO RUGGERO
· NOK −85,000 profit

EIENDOMSSELSKAPET CORSO RUGGERO has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIENDOMSSELSKAPET CORSO RUGGERO

Who owns EIENDOMSSELSKAPET CORSO RUGGERO?

KIRKHOLM HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of EIENDOMSSELSKAPET CORSO RUGGERO?

André Gauslaa Kirkholm is registered as general manager of EIENDOMSSELSKAPET CORSO RUGGERO.

Where is EIENDOMSSELSKAPET CORSO RUGGERO based?

EIENDOMSSELSKAPET CORSO RUGGERO has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.