BIZTRAC BETA
Sound recording and music publishing activities

SISTE STEG AS

Org. no. 999652840 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 498,000
Operating profit NOK −168,000
Equity NOK −218,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

SISTE STEG AS is registered as a limited company in Oslo, Oslo with organisation number 999652840. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Drive produksjon og distribusjon av musikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 498,000 in revenue and NOK −168,000 in operating profit.

Key figures · 2024

Revenue
NOK 498,000
Operating profit
NOK −168,000
Equity
NOK −218,000

Financial health · 2024

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

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

Who owns SISTE STEG AS?

PATRICK BOTTOLFSEN
SISTE STEG AS
NOK 498,000 rev. · NOK −168,000 profit

SISTE STEG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SISTE STEG AS

Who owns SISTE STEG AS?

PATRICK BOTTOLFSEN is the largest registered owner, with 37.5%.

What is the revenue of SISTE STEG AS?

SISTE STEG AS had revenue of NOK 498,000 in 2024.

Who is the general manager of SISTE STEG AS?

Magne Kristoffer Davidsen is registered as general manager of SISTE STEG AS.

Where is SISTE STEG AS based?

SISTE STEG AS has its business address in Oslo.

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.