BIZTRAC BETA
Other software publishing

MAESTRO SOFT AS

Org. no. 848072222 Limited company (AS) Oslo Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 117.8m
Operating profit NOK 33.9m
Equity NOK 9.1m
Incorporated 1988
Employees 41
Share capital NOK 200,000

Signals

1 flags
  • Nylig endring 2026-05-11 Adresseendring registrert 2026-05-11.

MAESTRO SOFT AS is registered as a limited company in Oslo, Oslo with organisation number 848072222. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 1988 and has 41 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Utvikle og selge programvare og tilhørende tjenester samt hva som hermed er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 117.8m in revenue and NOK 33.9m in operating profit.

Key figures · 2024

Revenue
NOK 117.8m
Operating profit
NOK 33.9m
Equity
NOK 9.1m
Est. value
NOK 158.8m

Financial health · 2024

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

Who owns MAESTRO SOFT AS?

MAESTRO AS
MAESTRO SOFT AS
NOK 117.8m rev. · NOK 33.9m profit

MAESTRO SOFT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MAESTRO SOFT AS er morselskap for 4 datterselskaper:

Frequently asked questions about MAESTRO SOFT AS

Who owns MAESTRO SOFT AS?

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

What is the revenue of MAESTRO SOFT AS?

MAESTRO SOFT AS had revenue of NOK 117.8m in 2024.

Who is the general manager of MAESTRO SOFT AS?

Øyvind Fonnes is registered as general manager of MAESTRO SOFT AS.

Where is MAESTRO SOFT AS based?

MAESTRO SOFT 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.