biztrac. BETA
COMPANY REGISTER PROFILE
989147110 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of motor vehicle parts and accessories

AUTOSOCK OPERATIONS AS

Org. no. 989147110 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 70.1m
Operating profit NOK 10.4m
Equity NOK 52.7m
Incorporated 2005
Share capital NOK 1.5m

AUTOSOCK OPERATIONS AS is registered as a limited company in Oslo, Oslo with organisation number 989147110. The business is classified under wholesale of motor vehicle parts and accessories (NACE 46.720). The company was incorporated in 2005. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Å produsere, selge og distribuere handelsprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 70.1m in revenue and NOK 10.4m in operating profit.

Key figures · 2025

Revenue
NOK 70.1m
▲ +24 %
Operating profit
NOK 10.4m
▲ +181 %
Equity
NOK 52.7m
▲ +17 %
Est. value
NOK 62.1m

Financial health · 2025

Liquidity
3.27
Very good
Current assets ÷ current liabilities
Profitability
15.0%
Good
Return on total assets
Solidity
69.9%
Very good
Equity as a share of total capital

Who owns AUTOSOCK OPERATIONS AS?

AUTOSOCK OPERATIONS AS
NOK 70.1m rev. · NOK 10.4m profit

AUTOSOCK OPERATIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUTOSOCK OPERATIONS AS

Who owns AUTOSOCK OPERATIONS AS?

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

What is the revenue of AUTOSOCK OPERATIONS AS?

AUTOSOCK OPERATIONS AS had revenue of NOK 70.1m in 2025.

Who is the general manager of AUTOSOCK OPERATIONS AS?

Odd Christian Krohn is registered as general manager of AUTOSOCK OPERATIONS AS.

Where is AUTOSOCK OPERATIONS AS based?

AUTOSOCK OPERATIONS 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.