BIZTRAC BETA
Security and commodity contracts brokerage

SB & SP RÅDGIVNING AS

Org. no. 929343166 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 1.5m
Equity NOK 744,000
Incorporated 2022
Share capital NOK 100,000

Signals

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

SB & SP RÅDGIVNING AS is registered as a limited company in Bergen, Vestland with organisation number 929343166. The business is classified under security and commodity contracts brokerage (NACE 66.120). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Tilby investeringsrådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 1.5m
Equity
NOK 744,000
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.5%
Good
Equity as a share of total capital

Who owns SB & SP RÅDGIVNING AS?

FH KAPITAL HOLDING AS
SB & SP RÅDGIVNING AS
NOK 6.1m rev. · NOK 1.5m profit

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

All shareholders and roles →

Frequently asked questions about SB & SP RÅDGIVNING AS

Who owns SB & SP RÅDGIVNING AS?

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

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

SB & SP RÅDGIVNING AS had revenue of NOK 6.1m in 2025.

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

Jan Frode Stuldalen is registered as general manager of SB & SP RÅDGIVNING AS.

Where is SB & SP RÅDGIVNING AS based?

SB & SP RÅDGIVNING AS has its business address in Bergen.

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.