BIZTRAC BETA
COMPANY REGISTER PROFILE
929453670 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

SYDSPISSEN AS

Org. no. 929453670 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 78,000
Operating profit NOK 65,000
Equity NOK 60,000
Incorporated 2022
Share capital NOK 30,000

SYDSPISSEN AS is registered as a limited company in Bergen, Vestland with organisation number 929453670. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i skipsfart, eiendom og annen næringsvirksomhet og kjøp og salg av verdipapirer samt hva hermed står i forbindendelse, herunder deltagelse i andre selskapet med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 78,000 in revenue and NOK 65,000 in operating profit.

Key figures · 2024

Revenue
NOK 78,000
Operating profit
NOK 65,000
Equity
NOK 60,000
Est. value
NOK 221,000

Financial health · 2024

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

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

Who owns SYDSPISSEN AS?

TORSTEIN VÅGE
SYDSPISSEN AS
NOK 78,000 rev. · NOK 65,000 profit

SYDSPISSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SYDSPISSEN AS own?

SYDSPISSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SYDSPISSEN AS

Who owns SYDSPISSEN AS?

TORSTEIN VÅGE is the largest registered owner, with 100.0%.

What is the revenue of SYDSPISSEN AS?

SYDSPISSEN AS had revenue of NOK 78,000 in 2024.

Where is SYDSPISSEN AS based?

SYDSPISSEN 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.