biztrac. BETA
COMPANY REGISTER PROFILE
922246033 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

EIMO AS

Org. no. 922246033 Limited company (AS) Stavanger Incorporated 2018 Active
Operating profit NOK −17,000
Equity NOK 108,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

EIMO AS is registered as a limited company in Stavanger, Rogaland with organisation number 922246033. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap. Oppføring og salg av bolig, bygg, fritidseiendom. Erverv og utleie av eiendom. Planrådgivning og boligrådgivning. Salg, salgsstøtte, kursing og foredrag. Analyseoppdrag. Medvirkning og eierskap i andre selskaper innen samme bransje er hovedformålet.”.

Key figures · 2025

Operating profit
NOK −17,000
▼ −7 %
Equity
NOK 108,000
▼ −14 %
Est. value
NOK 110,000

Financial health · 2025

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

Who owns EIMO AS?

EIMO AS
· NOK −17,000 profit

EIMO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIMO AS own?

EIMO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIMO AS

Who owns EIMO AS?

Eigir Malmgren Moberg is the largest registered owner, with 100.0%.

Who is the general manager of EIMO AS?

Eigir Malmgren Moberg is registered as general manager of EIMO AS.

Where is EIMO AS based?

EIMO AS has its business address in Talgje.

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.