BIZTRAC BETA
Other software publishing

RASTEREX SOFTWARE AS

Org. no. 984944675 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 661,000
Equity NOK 1.1m
Incorporated 2002
Share capital NOK 1.1m

RASTEREX SOFTWARE AS is registered as a limited company in Oslo, Oslo with organisation number 984944675. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2002. Registered share capital is NOK 1.1m, divided into 1100000 shares. The company's stated purpose is: “Utvikle, produsere, markedsføre og selge programvare for elektronisk dokumenthåndtering, rastereditering av tekniske dokumenter og DAK-relaterte moduler, samt alt som herved står i forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 661,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 661,000
Equity
NOK 1.1m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns RASTEREX SOFTWARE AS?

PCL HOLDING AS
RASTEREX SOFTWARE AS
NOK 7.5m rev. · NOK 661,000 profit

RASTEREX SOFTWARE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RASTEREX SOFTWARE AS

Who owns RASTEREX SOFTWARE AS?

PCL HOLDING AS is the largest registered owner, with 95.0%.

What is the revenue of RASTEREX SOFTWARE AS?

RASTEREX SOFTWARE AS had revenue of NOK 7.5m in 2024.

Who is the general manager of RASTEREX SOFTWARE AS?

Per Christian Lindstad is registered as general manager of RASTEREX SOFTWARE AS.

Where is RASTEREX SOFTWARE AS based?

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