BIZTRAC BETA
Accounting and bookkeeping

SISO REGNSKAP AS

Org. no. 930831255 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 22,000
Operating profit NOK −26,000
Equity NOK −39,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−39k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−26k kr).

SISO REGNSKAP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 930831255. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby regnskaps-, lønns-, og rådgivningstjenester innenfor økonomi og finans, samt virksomhet som naturlig henger sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 22,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 22,000
Operating profit
NOK −26,000
Equity
NOK −39,000

Financial health · 2024

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

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

Who owns SISO REGNSKAP AS?

SANDUM FINANS AS
SISO REGNSKAP AS
NOK 22,000 rev. · NOK −26,000 profit

SISO REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SISO REGNSKAP AS

Who owns SISO REGNSKAP AS?

SANDUM FINANS AS is the largest registered owner, with 100.0%.

What is the revenue of SISO REGNSKAP AS?

SISO REGNSKAP AS had revenue of NOK 22,000 in 2024.

Where is SISO REGNSKAP AS based?

SISO REGNSKAP AS has its business address in Lillestrøm.

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.