biztrac. BETA
COMPANY REGISTER PROFILE
818698712 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other activities auxiliary to financial services, except insurance and pension funding

PAYEX SVERIGE AB NUF

Org. no. 818698712 Norwegian division of foreign business enterprise (NUF) Oslo Active
Ownership graph ↗
Revenue 2025 SEK 991.9m
Operating profit SEK 8.5m
Equity SEK 2.6bn

PAYEX SVERIGE AB NUF is registered as a norwegian division of foreign business enterprise in Oslo, Oslo with organisation number 818698712. The business is classified under other activities auxiliary to financial services, except insurance and pension funding (NACE 66.190). The most recent filed accounts, for the 2025 financial year, show SEK 991.9m in revenue and SEK 8.5m in operating profit.

Former names: PAYEX SVERIGE AB

This company reports in SEK. The figures below are as filed, not converted to kroner. The top lists convert them to NOK at Norges Bank's rate for the end of the accounting year.

Key figures · 2025

Revenue
SEK 991.9m
▲ +91 %
Operating profit
SEK 8.5m
▼ −40 %
Equity
SEK 2.6bn
▲ +5132 %
Est. value
NOK 1.9bn

Financial health · 2025

Liquidity
1.84
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
43.6%
Very good
Equity as a share of total capital

Who owns PAYEX SVERIGE AB NUF?

No shareholders are registered for PAYEX SVERIGE AB NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PAYEX SVERIGE AB NUF

What is the revenue of PAYEX SVERIGE AB NUF?

PAYEX SVERIGE AB NUF had revenue of SEK 991.9m in 2025.

Who is the general manager of PAYEX SVERIGE AB NUF?

Raymond Klavestad is registered as general manager of PAYEX SVERIGE AB NUF.

Where is PAYEX SVERIGE AB NUF based?

PAYEX SVERIGE AB NUF has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.