BIZTRAC BETA
Rental and operating of own or leased real estate

ENGEL EIENDOM AS

Org. no. 930824801 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 52,000
Operating profit NOK −183,000
Equity NOK 77,000
Incorporated 2023
Share capital NOK 100,000

Signals

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

ENGEL EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 930824801. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investere i, eie, utvikle, drifte, forvalte og avhende eiendom, eiendomsselskap, eiendomsprosjekter og eiendomsrelaterte prosjekter og alt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 52,000 in revenue and NOK −183,000 in operating profit.

Key figures · 2024

Revenue
NOK 52,000
Operating profit
NOK −183,000
Equity
NOK 77,000
Est. value
NOK 117,000

Financial health · 2024

Liquidity
3632.74
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.0%
Weak
Equity as a share of total capital

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

Who owns ENGEL EIENDOM AS?

TM VERDI AS
ENGEL EIENDOM AS
NOK 52,000 rev. · NOK −183,000 profit

ENGEL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGEL EIENDOM AS

Who owns ENGEL EIENDOM AS?

TM VERDI AS is the largest registered owner, with 100.0%.

What is the revenue of ENGEL EIENDOM AS?

ENGEL EIENDOM AS had revenue of NOK 52,000 in 2024.

Where is ENGEL EIENDOM AS based?

ENGEL 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 15.06.2026.

Report a problem

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