BIZTRAC BETA
COMPANY REGISTER PROFILE
936560121 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

EON EIENDOM AS

Org. no. 936560121 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-14.

EON EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 936560121. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av eiendom og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Who owns EON EIENDOM AS?

No shareholders are registered for EON EIENDOM AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Group structure

EON EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about EON EIENDOM AS

Who is the general manager of EON EIENDOM AS?

Even Klepp Thorgersen is registered as general manager of EON EIENDOM AS.

Where is EON EIENDOM AS based?

EON EIENDOM AS has its business address in Oslo.

Property

Business address Dælenenggata 20B, 0567 Oslo
Cadastral unit 301-227/572/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 55 units

9 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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