biztrac. BETA
COMPANY REGISTER PROFILE
921205791 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

EBEM EIENDOM AS

Org. no. 921205791 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 5,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

EBEM EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 921205791. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, oppussing og utleie av fast eiendom, samt alt som hører naturlig med dette. Herunder også deltagelse i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▲ +69 %
Equity
NOK 5,000
▼ −53 %
Est. value
NOK 4,000

Financial health · 2025

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

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

Who owns EBEM EIENDOM AS?

EBEM EIENDOM AS
NOK 0 rev. · NOK −5,000 profit

EBEM EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EBEM EIENDOM AS

Who owns EBEM EIENDOM AS?

Erik Næsbak Brenden is the largest registered owner, with 50.0%.

What is the revenue of EBEM EIENDOM AS?

EBEM EIENDOM AS had revenue of NOK 0 in 2025.

Where is EBEM EIENDOM AS based?

EBEM 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.