BIZTRAC BETA
Uoppgitt

ESMOS HOLDING AS

Org. no. 835897362 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 0
Operating profit NOK −1,000
Equity NOK 22,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−1k kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

ESMOS HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 835897362. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns ESMOS HOLDING AS?

MONICA METHLIE SKØNBERG
ESMOS HOLDING AS
NOK 0 rev. · NOK −1,000 profit

ESMOS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ESMOS HOLDING AS own?

ESMOS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESMOS HOLDING AS

Who owns ESMOS HOLDING AS?

MONICA METHLIE SKØNBERG is the largest registered owner, with 50.0%.

What is the revenue of ESMOS HOLDING AS?

ESMOS HOLDING AS had revenue of NOK 0.

Where is ESMOS HOLDING AS based?

ESMOS HOLDING AS has its business address in Fyllingsdalen.

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.