BIZTRAC BETA
Industrial product and fashion design activities

SL EQUITIES AS

Org. no. 930798681 Limited company (AS) Orkland Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK 2,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

SL EQUITIES AS is registered as a limited company in Orkland, Trøndelag with organisation number 930798681. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer, samt annen virksomhet som har tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 2,000
Est. value
NOK 3,000

Financial health · 2025

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

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

Who owns SL EQUITIES AS?

IRENE LUSTERIO SCOTT
SL EQUITIES AS
NOK 0 rev. · NOK −20,000 profit

SL EQUITIES AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SL EQUITIES AS own?

SL EQUITIES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SL EQUITIES AS

Who owns SL EQUITIES AS?

IRENE LUSTERIO SCOTT is the largest registered owner, with 50.0%.

What is the revenue of SL EQUITIES AS?

SL EQUITIES AS had revenue of NOK 0 in 2025.

Where is SL EQUITIES AS based?

SL EQUITIES AS has its business address in Orkanger.

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.