BIZTRAC BETA
Buying and selling of own real estate

S-L HOLDING AS

Org. no. 922668531 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 801,000
Operating profit NOK 289,000
Equity NOK 1.0m
Incorporated 2019
Share capital NOK 30,000

S-L HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 922668531. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp/salg av eiendommer, investering i selskaper samt kjøp/salg av aksjer og alt som naturlig faller herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 801,000 in revenue and NOK 289,000 in operating profit.

Key figures · 2025

Revenue
NOK 801,000
Operating profit
NOK 289,000
Equity
NOK 1.0m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns S-L HOLDING AS?

SIMEN STRANDSET LØKKA
S-L HOLDING AS
NOK 801,000 rev. · NOK 289,000 profit

S-L HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S-L HOLDING AS own?

S-L HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about S-L HOLDING AS

Who owns S-L HOLDING AS?

SIMEN STRANDSET LØKKA is the largest registered owner, with 100.0%.

What is the revenue of S-L HOLDING AS?

S-L HOLDING AS had revenue of NOK 801,000 in 2025.

Who is the general manager of S-L HOLDING AS?

Simen Strandset Løkka is registered as general manager of S-L HOLDING AS.

Where is S-L HOLDING AS based?

S-L HOLDING AS has its business address in Sørumsand.

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.