BIZTRAC BETA
COMPANY REGISTER PROFILE
925047767 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other technical consultancy

NAMO EIENDOM ØSTLANDET AS

Org. no. 925047767 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Equity NOK 491,000
Incorporated 2020
Share capital NOK 500,000

NAMO EIENDOM ØSTLANDET AS is registered as a limited company in Bærum, Akershus with organisation number 925047767. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Salg av varer og tjenester til industri, verft og offshore installasjoner.”.

Former names: ELLINGSEN PIPETECH AS

Key figures · 2025

Equity
NOK 491,000
Est. value
NOK 242,000

Financial health · 2025

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

Who owns NAMO EIENDOM ØSTLANDET AS?

NAMO EIENDOM ØSTLANDET AS

NAMO EIENDOM ØSTLANDET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NAMO EIENDOM ØSTLANDET AS er morselskap for 4 datterselskaper:

Frequently asked questions about NAMO EIENDOM ØSTLANDET AS

Who owns NAMO EIENDOM ØSTLANDET AS?

NAMO HOLDING AS is the largest registered owner, with 100.0%.

Where is NAMO EIENDOM ØSTLANDET AS based?

NAMO EIENDOM ØSTLANDET AS has its business address in Skui.

Property

Business address Årenga 8, 1340 Skui
Cadastral unit 3201-77/247/0/0

4 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.