BIZTRAC BETA
Business and other management consultancy activities

STYRINGSPARTNER AS

Org. no. 918410996 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 207,000
Operating profit NOK −142,000
Equity NOK −168,000
Incorporated 2017
Share capital NOK 60,000

Signals

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

STYRINGSPARTNER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 918410996. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “å utøve konsulenttjenester innen eierstyring og selskapsledelse samt delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 207,000 in revenue and NOK −142,000 in operating profit.

Key figures · 2024

Revenue
NOK 207,000
Operating profit
NOK −142,000
Equity
NOK −168,000

Financial health · 2024

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

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

Who owns STYRINGSPARTNER AS?

JSY AS
STYRINGSPARTNER AS
NOK 207,000 rev. · NOK −142,000 profit

STYRINGSPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STYRINGSPARTNER AS

Who owns STYRINGSPARTNER AS?

JSY AS is the largest registered owner, with 100.0%.

What is the revenue of STYRINGSPARTNER AS?

STYRINGSPARTNER AS had revenue of NOK 207,000 in 2024.

Where is STYRINGSPARTNER AS based?

STYRINGSPARTNER AS has its business address in Trondheim.

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.