BIZTRAC BETA
Rental and operating of own or leased real estate

BARBAROSSA EIENDOM 2 AS

Org. no. 912253155 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 173,000
Operating profit NOK 137,000
Equity NOK 2,000
Incorporated 2013
Share capital NOK 740,000

BARBAROSSA EIENDOM 2 AS is registered as a limited company in Oslo, Oslo with organisation number 912253155. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 740,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 173,000 in revenue and NOK 137,000 in operating profit.

Key figures · 2024

Revenue
NOK 173,000
Operating profit
NOK 137,000
Equity
NOK 2,000
Est. value
NOK 236,000

Financial health · 2024

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

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

Who owns BARBAROSSA EIENDOM 2 AS?

PRIME APARTMENTS AS
BARBAROSSA EIENDOM 2 AS
NOK 173,000 rev. · NOK 137,000 profit

BARBAROSSA EIENDOM 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARBAROSSA EIENDOM 2 AS

Who owns BARBAROSSA EIENDOM 2 AS?

PRIME APARTMENTS AS is the largest registered owner, with 100.0%.

What is the revenue of BARBAROSSA EIENDOM 2 AS?

BARBAROSSA EIENDOM 2 AS had revenue of NOK 173,000 in 2024.

Who is the general manager of BARBAROSSA EIENDOM 2 AS?

Magribe Redjepi is registered as general manager of BARBAROSSA EIENDOM 2 AS.

Where is BARBAROSSA EIENDOM 2 AS based?

BARBAROSSA EIENDOM 2 AS has its business address in Oslo.

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.