BIZTRAC BETA
Activities of advertising agencies

SBS RÅDGIVNING AS

Org. no. 935247683 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 21,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

SBS RÅDGIVNING AS is registered as a limited company in Oslo, Oslo with organisation number 935247683. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å drive et reklamebyrå og tilby konsulenttjenester innen markedsføring, salg og tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 21,000
Est. value
NOK 34,000

Financial health · 2025

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

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

Who owns SBS RÅDGIVNING AS?

ELLEVE ELLEVE HOLDING AS
SBS RÅDGIVNING AS
NOK 0 rev. · NOK −2,000 profit

SBS RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SBS RÅDGIVNING AS

Who owns SBS RÅDGIVNING AS?

ELLEVE ELLEVE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SBS RÅDGIVNING AS?

SBS RÅDGIVNING AS had revenue of NOK 0 in 2025.

Who is the general manager of SBS RÅDGIVNING AS?

Torkel Skjolden is registered as general manager of SBS RÅDGIVNING AS.

Where is SBS RÅDGIVNING AS based?

SBS RÅDGIVNING 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.