BIZTRAC BETA
Computer programming activities

EATOPS AS

Org. no. 915700357 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 1.9m
Equity NOK 913,000
Incorporated 2015
Share capital NOK 300,000

EATOPS AS is registered as a limited company in Oslo, Oslo with organisation number 915700357. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2015. Registered share capital is NOK 300,000, divided into 6000 shares. The company's stated purpose is: “Å oppfinne, utforme, designe, utvikle og markedsføre ergonomiske programvaregrensesnitt for operative miljøer. I dette inngår alle finansielle, kommersielle og industrielle operasjoner, verdipapirer og fast eiendom som kan være direkte eller indirekte relatert til ovennevnte eller beslektede formål som kan utvikle aksjeselskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 1.9m
Equity
NOK 913,000
Est. value
NOK 7.9m

Financial health · 2025

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

Who owns EATOPS AS?

ALEXANDRE CEM ROGER VAN DAMME
EATOPS AS
NOK 5.3m rev. · NOK 1.9m profit

EATOPS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EATOPS AS

Who owns EATOPS AS?

ALEXANDRE CEM ROGER VAN DAMME is the largest registered owner, with 79.0%.

What is the revenue of EATOPS AS?

EATOPS AS had revenue of NOK 5.3m in 2025.

Who is the general manager of EATOPS AS?

Alexandre Cem Roger Van Damme is registered as general manager of EATOPS AS.

Where is EATOPS AS based?

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