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

EGIL VERNE AS

Org. no. 964476543 Limited company (AS) Oslo Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 201.5m
Operating profit NOK 35.0m
Equity NOK 30.0m
Incorporated 1992
Employees 30
Share capital NOK 500,000

EGIL VERNE AS is registered as a limited company in Oslo, Oslo with organisation number 964476543. The business is classified under wholesale of motor vehicle parts and accessories (NACE 46.720). The company was incorporated in 1992 and has 30 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Drive handel og investeringer. ”. The most recent filed accounts, for the 2025 financial year, show NOK 201.5m in revenue and NOK 35.0m in operating profit.

Key figures · 2025

Revenue
NOK 201.5m
▲ +8 %
Operating profit
NOK 35.0m
▲ +12 %
Equity
NOK 30.0m
▼ −13 %
Est. value
NOK 119.5m

Financial health · 2025

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
37.7%
Very good
Return on total assets
Solidity
31.3%
Good
Equity as a share of total capital

Who owns EGIL VERNE AS?

AXEL JOHNSON INTERNATIONAL AB SE
EGIL VERNE AS
NOK 201.5m rev. · NOK 35.0m profit

EGIL VERNE AS has 1 registered shareholder:

  • AXEL JOHNSON INTERNATIONAL AB 100.0%
All shareholders and roles →

Frequently asked questions about EGIL VERNE AS

Who owns EGIL VERNE AS?

AXEL JOHNSON INTERNATIONAL AB is the largest registered owner, with 100.0%.

What is the revenue of EGIL VERNE AS?

EGIL VERNE AS had revenue of NOK 201.5m in 2025.

Who is the general manager of EGIL VERNE AS?

Aleksander Ragnem is registered as general manager of EGIL VERNE AS.

Where is EGIL VERNE AS based?

EGIL VERNE 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.