BIZTRAC BETA
Activities of collection agencies and credit bureaus

INKASSOTJENESTER AS

Org. no. 938087164 Limited company (AS) Bærum Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 806,000
Equity NOK 2.2m
Incorporated 1986
Share capital NOK 500,000

INKASSOTJENESTER AS is registered as a limited company in Bærum, Akershus with organisation number 938087164. The business is classified under activities of collection agencies and credit bureaus (NACE 82.910). The company was incorporated in 1986. Registered share capital is NOK 500,000, divided into 6000 shares. The company's stated purpose is: “Oppfølging av utestående fordringer, inkassovirksomhet, herunder innhenting av gjenstander, formidling av lån, samt deltagelse i virksomhet som måtte stå i forbindelse med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 806,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 806,000
Equity
NOK 2.2m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns INKASSOTJENESTER AS?

KRAGVIN HOLDING AS
INKASSOTJENESTER AS
NOK 4.8m rev. · NOK 806,000 profit

INKASSOTJENESTER AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about INKASSOTJENESTER AS

Who owns INKASSOTJENESTER AS?

KRAGVIN HOLDING AS is the largest registered owner, with 67.6%.

What is the revenue of INKASSOTJENESTER AS?

INKASSOTJENESTER AS had revenue of NOK 4.8m in 2025.

Who is the general manager of INKASSOTJENESTER AS?

Bjørn Vines is registered as general manager of INKASSOTJENESTER AS.

Where is INKASSOTJENESTER AS based?

INKASSOTJENESTER AS has its business address in Sandvika.

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.