BIZTRAC BETA
Rental and operating of own or leased real estate

EIDEL EIENDOM AS

Org. no. 980447030 Limited company (AS) Eidsvoll Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 909,000
Operating profit NOK −135,000
Equity NOK 11.3m
Incorporated 1998
Share capital NOK 4.0m

Signals

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

EIDEL EIENDOM AS is registered as a limited company in Eidsvoll, Akershus with organisation number 980447030. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 4.0m, divided into 4000 shares. The company's stated purpose is: “Bygge og leie ut eiendom, samt hva hermed står i forbindelse, og å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 909,000 in revenue and NOK −135,000 in operating profit.

Key figures · 2025

Revenue
NOK 909,000
Operating profit
NOK −135,000
Equity
NOK 11.3m
Est. value
NOK 9.1m

Financial health · 2025

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

Who owns EIDEL EIENDOM AS?

BRASH AS
EIDEL EIENDOM AS
NOK 909,000 rev. · NOK −135,000 profit

EIDEL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIDEL EIENDOM AS

Who owns EIDEL EIENDOM AS?

BRASH AS is the largest registered owner, with 100.0%.

What is the revenue of EIDEL EIENDOM AS?

EIDEL EIENDOM AS had revenue of NOK 909,000 in 2025.

Who is the general manager of EIDEL EIENDOM AS?

Øystein Sandholt is registered as general manager of EIDEL EIENDOM AS.

Where is EIDEL EIENDOM AS based?

EIDEL EIENDOM AS has its business address in Eidsvoll.

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.