BIZTRAC BETA
Computer programming activities

MAD SOFTWARE AS

Org. no. 930585548 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 189,000
Operating profit NOK −60,000
Equity NOK 7.1m
Incorporated 2022
Share capital NOK 38,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−60k kr).
  • Nylig endring 2026-03-03 Adresseendring registrert 2026-03-03.

MAD SOFTWARE AS is registered as a limited company in Oslo, Oslo with organisation number 930585548. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 38,000, divided into 3785695 shares. The company's stated purpose is: “Utvikling og salg av software, AI og algoritmebasert teknologi, samt drift og servicevirksomhet tilknyttet dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 189,000 in revenue and NOK −60,000 in operating profit.

Key figures · 2024

Revenue
NOK 189,000
Operating profit
NOK −60,000
Equity
NOK 7.1m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns MAD SOFTWARE AS?

SVEN ARILD BJØRNSTAD
MAD SOFTWARE AS
NOK 189,000 rev. · NOK −60,000 profit

MAD SOFTWARE AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about MAD SOFTWARE AS

Who owns MAD SOFTWARE AS?

SVEN ARILD BJØRNSTAD is the largest registered owner, with 39.6%.

What is the revenue of MAD SOFTWARE AS?

MAD SOFTWARE AS had revenue of NOK 189,000 in 2024.

Who is the general manager of MAD SOFTWARE AS?

Eivind Linge is registered as general manager of MAD SOFTWARE AS.

Where is MAD SOFTWARE AS based?

MAD SOFTWARE 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.