BIZTRAC BETA
Wholesale of clothing and footwear

AASEN TRADING AS

Org. no. 989862073 Limited company (AS) Nord-Fron Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 317,000
Equity NOK 1.1m
Incorporated 2006
Share capital NOK 30,000

AASEN TRADING AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 989862073. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Grossist- og detaljhandel innen manufaktur, samt ved aksjetegning eller på annen måte gjøre seg interessert i annen virksomhet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 317,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 317,000
Equity
NOK 1.1m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns AASEN TRADING AS?

TOM ERIK AULIE ÅSEN
AASEN TRADING AS
NOK 3.9m rev. · NOK 317,000 profit

AASEN TRADING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AASEN TRADING AS own?

AASEN TRADING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AASEN TRADING AS

Who owns AASEN TRADING AS?

TOM ERIK AULIE ÅSEN is the largest registered owner, with 100.0%.

What is the revenue of AASEN TRADING AS?

AASEN TRADING AS had revenue of NOK 3.9m in 2024.

Who is the general manager of AASEN TRADING AS?

Tom Erik Aulie Åsen is registered as general manager of AASEN TRADING AS.

Where is AASEN TRADING AS based?

AASEN TRADING AS has its business address in Vinstra.

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.