BIZTRAC BETA
Rental and operating of own or leased real estate

ENSE EIENDOM AS

Org. no. 925580511 Limited company (AS) Aurskog-Høland Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 155,000
Operating profit NOK 112,000
Equity NOK −65,000
Incorporated 2020
Share capital NOK 40,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−65k kr).

ENSE EIENDOM AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 925580511. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Investeringer i eiendom, aksjer og andre verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 155,000 in revenue and NOK 112,000 in operating profit.

Key figures · 2024

Revenue
NOK 155,000
Operating profit
NOK 112,000
Equity
NOK −65,000
Est. value
NOK 764,000

Financial health · 2024

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

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

Who owns ENSE EIENDOM AS?

SOLHOLMEN ØST AS
ENSE EIENDOM AS
NOK 155,000 rev. · NOK 112,000 profit

ENSE EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENSE EIENDOM AS

Who owns ENSE EIENDOM AS?

SOLHOLMEN ØST AS is the largest registered owner, with 50.0%.

What is the revenue of ENSE EIENDOM AS?

ENSE EIENDOM AS had revenue of NOK 155,000 in 2024.

Who is the general manager of ENSE EIENDOM AS?

Roar Sether is registered as general manager of ENSE EIENDOM AS.

Where is ENSE EIENDOM AS based?

ENSE EIENDOM AS has its business address in Bjørkelangen.

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.