BIZTRAC BETA
Intermediation service activities for business support service activities n.e.c.

GJELDSOPPRYDDING AS

Org. no. 963771398 Limited company (AS) Lunner Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 530,000
Operating profit NOK 162,000
Equity NOK 971,000
Incorporated 1991
Share capital NOK 100,000

GJELDSOPPRYDDING AS is registered as a limited company in Lunner, Akershus with organisation number 963771398. The business is classified under intermediation service activities for business support service activities n.e.c. (NACE 82.400). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å hjelpe kunder med opprydding og refinansiering av gjeld, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 530,000 in revenue and NOK 162,000 in operating profit.

Key figures · 2024

Revenue
NOK 530,000
Operating profit
NOK 162,000
Equity
NOK 971,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns GJELDSOPPRYDDING AS?

HANS BRYNJULF SAGBAKKEN
GJELDSOPPRYDDING AS
NOK 530,000 rev. · NOK 162,000 profit

GJELDSOPPRYDDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJELDSOPPRYDDING AS

Who owns GJELDSOPPRYDDING AS?

HANS BRYNJULF SAGBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of GJELDSOPPRYDDING AS?

GJELDSOPPRYDDING AS had revenue of NOK 530,000 in 2024.

Who is the general manager of GJELDSOPPRYDDING AS?

Hans Brynjulf Sagbakken is registered as general manager of GJELDSOPPRYDDING AS.

Where is GJELDSOPPRYDDING AS based?

GJELDSOPPRYDDING AS has its business address in Lunner.

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.