BIZTRAC BETA
Retail sale of clothing

SLOANE AS

Org. no. 996927598 Limited company (AS) Sandnes Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 346,000
Operating profit NOK −160,000
Equity NOK 7.8m
Incorporated 2011
Share capital NOK 100,000

Signals

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

SLOANE AS is registered as a limited company in Sandnes, Rogaland with organisation number 996927598. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 125 shares. The company's stated purpose is: “Eie og investere i aksjer og andre selskaper og virksomheter, samt deltakelse av enhver art i andre virksomheter og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 346,000 in revenue and NOK −160,000 in operating profit.

Key figures · 2025

Revenue
NOK 346,000
Operating profit
NOK −160,000
Equity
NOK 7.8m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns SLOANE AS?

LASSE VICTOR LEDAAL
SLOANE AS
NOK 346,000 rev. · NOK −160,000 profit

SLOANE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SLOANE AS own?

SLOANE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SLOANE AS

Who owns SLOANE AS?

LASSE VICTOR LEDAAL is the largest registered owner, with 80.0%.

What is the revenue of SLOANE AS?

SLOANE AS had revenue of NOK 346,000 in 2025.

Who is the general manager of SLOANE AS?

Jon Ledaal is registered as general manager of SLOANE AS.

Where is SLOANE AS based?

SLOANE AS has its business address in Sandnes.

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.