BIZTRAC BETA
Accounting and bookkeeping

SL REGNSKAP AS

Org. no. 915119050 Limited company (AS) Ulstein Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 134,000
Operating profit NOK −13,000
Equity NOK 25,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

SL REGNSKAP AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 915119050. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Regnskapsføring og konsulenttjenester innen administrasjon og organisasjonsteknisk tjenesteyting.”. The most recent filed accounts, for the 2024 financial year, show NOK 134,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 134,000
Operating profit
NOK −13,000
Equity
NOK 25,000
Est. value
NOK 153,000

Financial health · 2024

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

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

Who owns SL REGNSKAP AS?

STILILL INVEST AS
SL REGNSKAP AS
NOK 134,000 rev. · NOK −13,000 profit

SL REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SL REGNSKAP AS

Who owns SL REGNSKAP AS?

STILILL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SL REGNSKAP AS?

SL REGNSKAP AS had revenue of NOK 134,000 in 2024.

Who is the general manager of SL REGNSKAP AS?

Stian Lillestøl is registered as general manager of SL REGNSKAP AS.

Where is SL REGNSKAP AS based?

SL REGNSKAP AS has its business address in Ulsteinvik.

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.