BIZTRAC BETA
Activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods

SOLHEIM SKO AS

Org. no. 968621467 Limited company (AS) Bærum Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −41,000
Equity NOK 339,000
Incorporated 1994
Share capital NOK 31,000

Signals

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

SOLHEIM SKO AS is registered as a limited company in Bærum, Akershus with organisation number 968621467. The business is classified under activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods (NACE 46.160). The company was incorporated in 1994. Registered share capital is NOK 31,000, divided into 102 shares. The company's stated purpose is: “Handelsagentur med tyske skoprodukter under varemerket ARA.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −41,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −41,000
Equity
NOK 339,000
Est. value
NOK 777,000

Financial health · 2025

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

Who owns SOLHEIM SKO AS?

JACOB SOLHEIM
SOLHEIM SKO AS
NOK 1.9m rev. · NOK −41,000 profit

SOLHEIM SKO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLHEIM SKO AS

Who owns SOLHEIM SKO AS?

JACOB SOLHEIM is the largest registered owner, with 56.9%.

What is the revenue of SOLHEIM SKO AS?

SOLHEIM SKO AS had revenue of NOK 1.9m in 2025.

Who is the general manager of SOLHEIM SKO AS?

Svein Martin Lundbye is registered as general manager of SOLHEIM SKO AS.

Where is SOLHEIM SKO AS based?

SOLHEIM SKO AS has its business address in Fornebu.

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.