BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

SCHELLHORN AS

Org. no. 992182571 Limited company (AS) Kristiansand Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 62.5m
Operating profit NOK 1.6m
Equity NOK 1.5m
Incorporated 2008
Employees 19
Share capital NOK 500,000

SCHELLHORN AS is registered as a limited company in Kristiansand, Agder with organisation number 992182571. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2008 and has 19 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjenom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 62.5m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 62.5m
Operating profit
NOK 1.6m
Equity
NOK 1.5m
Est. value
NOK 7.0m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.0%
Satisfactory
Equity as a share of total capital

Who owns SCHELLHORN AS?

ERIK SCHELLHORN
SCHELLHORN AS
NOK 62.5m rev. · NOK 1.6m profit

SCHELLHORN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SCHELLHORN AS

Who owns SCHELLHORN AS?

ERIK SCHELLHORN is the largest registered owner, with 100.0%.

What is the revenue of SCHELLHORN AS?

SCHELLHORN AS had revenue of NOK 62.5m in 2025.

Who is the general manager of SCHELLHORN AS?

Erik Schellhorn is registered as general manager of SCHELLHORN AS.

Where is SCHELLHORN AS based?

SCHELLHORN AS has its business address in Kristiansand S.

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.