BIZTRAC BETA
Business and other management consultancy activities

SLUPPEN & PARTNERS AS

Org. no. 913287509 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK −1.7m
Equity NOK 528,000
Incorporated 2014
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

SLUPPEN & PARTNERS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913287509. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Være en innovasjonsplattform og møtested for etablert næringsliv, akademia, studenter og oppstartsbedrifter på Sluppen i Trondheim, og det som ellers naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK −1.7m
Equity
NOK 528,000
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns SLUPPEN & PARTNERS AS?

R KJELDSBERG AS
SLUPPEN & PARTNERS AS
NOK 2.4m rev. · NOK −1.7m profit

SLUPPEN & PARTNERS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLUPPEN & PARTNERS AS

Who owns SLUPPEN & PARTNERS AS?

R KJELDSBERG AS is the largest registered owner, with 100.0%.

What is the revenue of SLUPPEN & PARTNERS AS?

SLUPPEN & PARTNERS AS had revenue of NOK 2.4m in 2024.

Where is SLUPPEN & PARTNERS AS based?

SLUPPEN & PARTNERS 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.