BIZTRAC BETA
Computer programming activities

MOLENDO AS

Org. no. 929081838 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 34.7m
Operating profit NOK 2.0m
Equity NOK 2.4m
Incorporated 2022
Employees 31
Share capital NOK 100,000

Signals

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

MOLENDO AS is registered as a limited company in Oslo, Oslo with organisation number 929081838. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022 and has 31 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Nettbutikk, rådgivningstjenester, utvikling av software og annen tilknyttet virksomhet i Norge og utlandet, herunder ervervelse av selskaper som står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.7m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 34.7m
Operating profit
NOK 2.0m
Equity
NOK 2.4m
Est. value
NOK 12.6m

Financial health · 2024

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.2%
Good
Equity as a share of total capital

Who owns MOLENDO AS?

ELLING AS
MOLENDO AS
NOK 34.7m rev. · NOK 2.0m profit

MOLENDO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOLENDO AS

Who owns MOLENDO AS?

ELLING AS is the largest registered owner, with 100.0%.

What is the revenue of MOLENDO AS?

MOLENDO AS had revenue of NOK 34.7m in 2024.

Who is the general manager of MOLENDO AS?

Kjell Ove Kvalheim is registered as general manager of MOLENDO AS.

Where is MOLENDO AS based?

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