biztrac. BETA
COMPANY REGISTER PROFILE
968851217 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other printing

PROFILERINGS-SPESIALISTEN AS

Org. no. 968851217 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 42.9m
Operating profit NOK −638,000
Equity NOK 17.4m
Incorporated 1993
Employees 7
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−638k kr).

PROFILERINGS-SPESIALISTEN AS is registered as a limited company in Oslo, Oslo with organisation number 968851217. The business is classified under other printing (NACE 18.120). The company was incorporated in 1993 and has 7 registered employees. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Handelsvirksomhet, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 42.9m in revenue and NOK −638,000 in operating profit.

Former names: PROFILERINGSPESIALISTEN AS

Key figures · 2025

Revenue
NOK 42.9m
▲ +16 %
Operating profit
NOK −638,000
▲ +44 %
Equity
NOK 17.4m
▼ −3 %
Est. value
NOK 15.1m

Financial health · 2025

Liquidity
4.06
Very good
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
75.5%
Very good
Equity as a share of total capital

Who owns PROFILERINGS-SPESIALISTEN AS?

PROFILERINGS-SPESIALISTEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROFILERINGS-SPESIALISTEN AS

Who owns PROFILERINGS-SPESIALISTEN AS?

Tommy William Olsen is the largest registered owner, with 40.0%.

What is the revenue of PROFILERINGS-SPESIALISTEN AS?

PROFILERINGS-SPESIALISTEN AS had revenue of NOK 42.9m in 2025.

Where is PROFILERINGS-SPESIALISTEN AS based?

PROFILERINGS-SPESIALISTEN AS 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.