BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

EXPERIAN GJELDSREGISTER AS

Org. no. 920438679 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 9.9m
Operating profit NOK 3.4m
Equity NOK 9.9m
Incorporated 2018
Share capital NOK 60,000

EXPERIAN GJELDSREGISTER AS is registered as a limited company in Bærum, Akershus with organisation number 920438679. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Å drive all virksomhet som naturlig hører inn under drift av gjeldsregister.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.9m in revenue and NOK 3.4m in operating profit.

Key figures · 2025

Revenue
NOK 9.9m
Operating profit
NOK 3.4m
Equity
NOK 9.9m
Est. value
NOK 19.5m

Financial health · 2025

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

Who owns EXPERIAN GJELDSREGISTER AS?

EXPERIAN AS
EXPERIAN GJELDSREGISTER AS
NOK 9.9m rev. · NOK 3.4m profit

EXPERIAN GJELDSREGISTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EXPERIAN GJELDSREGISTER AS

Who owns EXPERIAN GJELDSREGISTER AS?

EXPERIAN AS is the largest registered owner, with 100.0%.

What is the revenue of EXPERIAN GJELDSREGISTER AS?

EXPERIAN GJELDSREGISTER AS had revenue of NOK 9.9m in 2025.

Who is the general manager of EXPERIAN GJELDSREGISTER AS?

Tobias Daman is registered as general manager of EXPERIAN GJELDSREGISTER AS.

Where is EXPERIAN GJELDSREGISTER AS based?

EXPERIAN GJELDSREGISTER AS has its business address in Lysaker.

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.