BIZTRAC BETA
Uoppgitt

EBM-INVEST AS

Org. no. 934081625 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK −115
Operating profit NOK −2,000
Equity NOK 28,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

EBM-INVEST AS is registered as a limited company in Asker, Akershus with organisation number 934081625. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2024 financial year, show NOK −115 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK −115
Operating profit
NOK −2,000
Equity
NOK 28,000
Est. value
NOK 33,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EBM-INVEST AS?

ESPEN BJØRKENG MÆRLI
EBM-INVEST AS
NOK −115 rev. · NOK −2,000 profit

EBM-INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EBM-INVEST AS own?

EBM-INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EBM-INVEST AS

Who owns EBM-INVEST AS?

ESPEN BJØRKENG MÆRLI is the largest registered owner, with 100.0%.

What is the revenue of EBM-INVEST AS?

EBM-INVEST AS had revenue of NOK −115 in 2024.

Where is EBM-INVEST AS based?

EBM-INVEST AS has its business address in Vollen.

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.