biztrac. BETA
COMPANY REGISTER PROFILE
920601383 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

XSPERTO AS

Org. no. 920601383 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 37.1m
Operating profit NOK 7.3m
Equity NOK 4.9m
Incorporated 2018
Share capital NOK 30,000

XSPERTO AS is registered as a limited company in Drammen, Buskerud with organisation number 920601383. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Økonomisk rådgivning og tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 37.1m in revenue and NOK 7.3m in operating profit.

Former names: ALFANOR 18125 AS

Key figures · 2025

Revenue
NOK 37.1m
▲ +184 %
Operating profit
NOK 7.3m
▲ +450 %
Equity
NOK 4.9m
▲ +50 %
Est. value
NOK 28.7m

Financial health · 2025

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
56.5%
Very good
Return on total assets
Solidity
29.6%
Good
Equity as a share of total capital

Who owns XSPERTO AS?

XSPERTO AS
NOK 37.1m rev. · NOK 7.3m profit

XSPERTO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does XSPERTO AS own?

XSPERTO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about XSPERTO AS

Who owns XSPERTO AS?

Frank Sverre Rognli is the largest registered owner, with 100.0%.

What is the revenue of XSPERTO AS?

XSPERTO AS had revenue of NOK 37.1m in 2025.

Who is the general manager of XSPERTO AS?

Frank Sverre Rognli is registered as general manager of XSPERTO AS.

Where is XSPERTO AS based?

XSPERTO AS has its business address in Drammen.

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.