BIZTRAC BETA
Retail sale of textiles

SKANDUN AS

Org. no. 889181192 Limited company (AS) Indre Østfold Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK −4.7m
Equity NOK 61.6m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,7 mill kr).

SKANDUN AS is registered as a limited company in Indre Østfold, Østfold with organisation number 889181192. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringer i aksjer, andre verdipapirer og fast eiendom samt kjøp, salg og formidling av kunstverk og deltagelse i virksomhet av lignende karakter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK −4.7m in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK −4.7m
Equity
NOK 61.6m
Est. value
NOK 56.1m

Financial health · 2024

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

Who owns SKANDUN AS?

STEIN LIE
SKANDUN AS
NOK 1.3m rev. · NOK −4.7m profit

SKANDUN AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SKANDUN AS own?

SKANDUN AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about SKANDUN AS

Who owns SKANDUN AS?

STEIN LIE is the largest registered owner, with 91.0%.

What is the revenue of SKANDUN AS?

SKANDUN AS had revenue of NOK 1.3m in 2024.

Who is the general manager of SKANDUN AS?

Stein Lie is registered as general manager of SKANDUN AS.

Where is SKANDUN AS based?

SKANDUN AS has its business address in Askim.

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.