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

EBE-2 EIENDOM AS

Org. no. 913693507 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −5.1m
Equity NOK −25.7m
Incorporated 2014
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−25,7 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5,1 mill kr).

EBE-2 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 913693507. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utleie, drift, kjøp og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tillegg kommer annen nærliggende virksomhet.”.

Key figures · 2025

Operating profit
NOK −5.1m
▼ −202 %
Equity
NOK −25.7m
▼ −43 %

Financial health · 2025

Liquidity
40.90
Very good
Current assets ÷ current liabilities
Profitability
1.4%
Weak
Return on total assets
Solidity
-20.5%
Weak
Equity as a share of total capital

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

Who owns EBE-2 EIENDOM AS?

EBE-2 EIENDOM AS
· NOK −5.1m profit

EBE-2 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EBE-2 EIENDOM AS own?

EBE-2 EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EBE-2 EIENDOM AS

Who owns EBE-2 EIENDOM AS?

RAGDE EIENDOM AS is the largest registered owner, with 100.0%.

Where is EBE-2 EIENDOM AS based?

EBE-2 EIENDOM 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 03.10.2026.

Report a problem

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