BIZTRAC BETA
Computer consultancy and computer facilities management activities

CATALYZER AS

Org. no. 993146714 Limited company (AS) Nesbyen Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 46,000
Operating profit NOK −137,000
Equity NOK 145,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−137k kr).

CATALYZER AS is registered as a limited company in Nesbyen, Buskerud with organisation number 993146714. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av IT tjenester med tilhørende salg av IT-relatert handels produkter herunder investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 46,000 in revenue and NOK −137,000 in operating profit.

Key figures · 2024

Revenue
NOK 46,000
Operating profit
NOK −137,000
Equity
NOK 145,000
Est. value
NOK 143,000

Financial health · 2024

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

Who owns CATALYZER AS?

MAGNUS KARLSEN REITEN
CATALYZER AS
NOK 46,000 rev. · NOK −137,000 profit

CATALYZER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CATALYZER AS

Who owns CATALYZER AS?

MAGNUS KARLSEN REITEN is the largest registered owner, with 50.0%.

What is the revenue of CATALYZER AS?

CATALYZER AS had revenue of NOK 46,000 in 2024.

Who is the general manager of CATALYZER AS?

Magne Andre Gullingsrud is registered as general manager of CATALYZER AS.

Where is CATALYZER AS based?

CATALYZER AS has its business address in Nesbyen.

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.