BIZTRAC BETA
Computer programming activities

BRICKS SOFTWARE AS

Org. no. 922998337 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 26.6m
Operating profit NOK −32.4m
Equity NOK 45.3m
Incorporated 2019
Employees 8
Share capital NOK 77,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−32,4 mill kr).
  • Nylig endring 2026-03-30 Aksjekapital registrert 2026-03-30.

BRICKS SOFTWARE AS is registered as a limited company in Oslo, Oslo with organisation number 922998337. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 77,000, divided into 76605589 shares. The company's stated purpose is: “Internettdesign og programmering.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.6m in revenue and NOK −32.4m in operating profit.

Key figures · 2024

Revenue
NOK 26.6m
Operating profit
NOK −32.4m
Equity
NOK 45.3m
Est. value
NOK 65.4m

Financial health · 2024

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

Who owns BRICKS SOFTWARE AS?

CONRADI INVEST AS
BRICKS SOFTWARE AS
NOK 26.6m rev. · NOK −32.4m profit

BRICKS SOFTWARE AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does BRICKS SOFTWARE AS own?

BRICKS SOFTWARE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRICKS SOFTWARE AS

Who owns BRICKS SOFTWARE AS?

CONRADI INVEST AS is the largest registered owner, with 25.2%.

What is the revenue of BRICKS SOFTWARE AS?

BRICKS SOFTWARE AS had revenue of NOK 26.6m in 2024.

Where is BRICKS SOFTWARE AS based?

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