BIZTRAC BETA
Rental and operating of own or leased real estate

EIKSMARKA NÆRINGSBYGG AS

Org. no. 940235618 Limited company (AS) Bærum Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 535,000
Equity NOK 6.2m
Incorporated 1986
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EIKSMARKA NÆRINGSBYGG AS is registered as a limited company in Bærum, Akershus with organisation number 940235618. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 30,000, divided into 14 shares. The company's stated purpose is: “Å drifte og utvikle eiendom i Bærum kommune. Videre kan selskapet delta i andre selskaper med beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 535,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 535,000
Equity
NOK 6.2m
Est. value
NOK 5.7m

Financial health · 2025

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

Who owns EIKSMARKA NÆRINGSBYGG AS?

BACKE PROSJEKT AS
EIKSMARKA NÆRINGSBYGG AS
NOK 1.9m rev. · NOK 535,000 profit

EIKSMARKA NÆRINGSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKSMARKA NÆRINGSBYGG AS

Who owns EIKSMARKA NÆRINGSBYGG AS?

BACKE PROSJEKT AS is the largest registered owner, with 100.0%.

What is the revenue of EIKSMARKA NÆRINGSBYGG AS?

EIKSMARKA NÆRINGSBYGG AS had revenue of NOK 1.9m in 2025.

Where is EIKSMARKA NÆRINGSBYGG AS based?

EIKSMARKA NÆRINGSBYGG AS has its business address in Lysaker.

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.