BIZTRAC BETA
Computer programming activities

ESSOF BIDCO AS

Org. no. 933310132 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −2.1m
Equity NOK 1.6bn
Incorporated 2024
Share capital NOK 34,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,1 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-24 Aksjekapital registrert 2026-04-24.

ESSOF BIDCO AS is registered as a limited company in Oslo, Oslo with organisation number 933310132. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 34,000, divided into 1000 shares. The company's stated purpose is: “Direkte eller indirekte eie og forvalte verdipapirer, eiendom og løsøre sammen med alle andre virksomhetsaktiviteter relatert til dette, samt tilby tjenester til andre tilknyttede selskaper i forbindelse med administrasjon, ledelse markedsføring og alle andre virksomhetsrelaterte aktiviteter.”.

Key figures · 2024

Operating profit
NOK −2.1m
Equity
NOK 1.6bn
Est. value
NOK 3.0bn

Financial health · 2024

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

Who owns ESSOF BIDCO AS?

ESSOF MIDCO AS
ESSOF BIDCO AS
· NOK −2.1m profit

ESSOF BIDCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESSOF BIDCO AS own?

ESSOF BIDCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESSOF BIDCO AS

Who owns ESSOF BIDCO AS?

ESSOF MIDCO AS is the largest registered owner, with 100.0%.

Where is ESSOF BIDCO AS based?

ESSOF BIDCO AS has its business address in Oslo.

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.