BIZTRAC BETA
Sports activities n.e.c.

AASEN-INVEST AS

Org. no. 928034291 Limited company (AS) Sarpsborg Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 39,000
Incorporated 2021
Share capital NOK 50,000

Signals

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

AASEN-INVEST AS is registered as a limited company in Sarpsborg, Østfold with organisation number 928034291. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Investere i aksjer og andeler og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 39,000
Est. value
NOK 49,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AASEN-INVEST AS?

BENJAMIN ANDRÉ AASEN
AASEN-INVEST AS
NOK 0 rev. · NOK −4,000 profit

AASEN-INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AASEN-INVEST AS own?

AASEN-INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

AASEN-INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about AASEN-INVEST AS

Who owns AASEN-INVEST AS?

BENJAMIN ANDRÉ AASEN is the largest registered owner, with 100.0%.

What is the revenue of AASEN-INVEST AS?

AASEN-INVEST AS had revenue of NOK 0 in 2025.

Where is AASEN-INVEST AS based?

AASEN-INVEST AS has its business address in Ise.

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.