BIZTRAC BETA
Accounting and bookkeeping

SL KONSULT AS

Org. no. 916030940 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 253,000
Operating profit NOK 233,000
Equity NOK 269,000
Incorporated 2015
Share capital NOK 32,000

Signals

1 flags
  • Nylig endring 2026-03-13 Aksjekapital registrert 2026-03-13.

SL KONSULT AS is registered as a limited company in Asker, Akershus with organisation number 916030940. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2015. Registered share capital is NOK 32,000, divided into 105 shares. The company's stated purpose is: “Levere regnskap- og rådgivnings-tjenester. Selskapet skal også investere eller delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 253,000 in revenue and NOK 233,000 in operating profit.

Key figures · 2025

Revenue
NOK 253,000
Operating profit
NOK 233,000
Equity
NOK 269,000
Est. value
NOK 911,000

Financial health · 2025

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

Who owns SL KONSULT AS?

SIMEN LEREIM
SL KONSULT AS
NOK 253,000 rev. · NOK 233,000 profit

SL KONSULT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SL KONSULT AS own?

SL KONSULT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SL KONSULT AS

Who owns SL KONSULT AS?

SIMEN LEREIM is the largest registered owner, with 100.0%.

What is the revenue of SL KONSULT AS?

SL KONSULT AS had revenue of NOK 253,000 in 2025.

Who is the general manager of SL KONSULT AS?

Simen Lereim is registered as general manager of SL KONSULT AS.

Where is SL KONSULT AS based?

SL KONSULT AS has its business address in Asker.

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.