BIZTRAC BETA
Security and commodity contracts brokerage

JS & SP RÅDGIVNING AS

Org. no. 926054554 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 9.5m
Operating profit NOK 4.1m
Equity NOK 4.5m
Incorporated 2020
Share capital NOK 235,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JS & SP RÅDGIVNING AS is registered as a limited company in Drammen, Buskerud with organisation number 926054554. The business is classified under security and commodity contracts brokerage (NACE 66.120). The company was incorporated in 2020. Registered share capital is NOK 235,000, divided into 196078 shares. The company's stated purpose is: “Tilby investeringsrådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.5m in revenue and NOK 4.1m in operating profit.

Key figures · 2025

Revenue
NOK 9.5m
Operating profit
NOK 4.1m
Equity
NOK 4.5m
Est. value
NOK 12.6m

Financial health · 2025

Liquidity
3.54
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.5%
Good
Equity as a share of total capital

Who owns JS & SP RÅDGIVNING AS?

FH KAPITAL HOLDING AS
JS & SP RÅDGIVNING AS
NOK 9.5m rev. · NOK 4.1m profit

JS & SP RÅDGIVNING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JS & SP RÅDGIVNING AS

Who owns JS & SP RÅDGIVNING AS?

FH KAPITAL HOLDING AS is the largest registered owner, with 51.0%.

What is the revenue of JS & SP RÅDGIVNING AS?

JS & SP RÅDGIVNING AS had revenue of NOK 9.5m in 2025.

Who is the general manager of JS & SP RÅDGIVNING AS?

Jonas Bagstevold is registered as general manager of JS & SP RÅDGIVNING AS.

Where is JS & SP RÅDGIVNING AS based?

JS & SP RÅDGIVNING AS has its business address in Drammen.

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.