BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

SPON VERKSTED AS

Org. no. 932950081 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −59,000
Equity NOK −29,000
Incorporated 2024
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−29k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−59k kr).

SPON VERKSTED AS is registered as a limited company in Oslo, Oslo with organisation number 932950081. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2024 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie av verkstedplass med tilhørende verktøy og maskiner, samt tilby kurs og opplæring i verktøybruk og snekring. Selskapet skal også drive med annen virksomhet som naturlig hører sammen med dette.”.

Key figures · 2024

Operating profit
NOK −59,000
Equity
NOK −29,000

Financial health · 2024

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

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

Who owns SPON VERKSTED AS?

NEXTASCENT AS
SPON VERKSTED AS
· NOK −59,000 profit

SPON VERKSTED AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPON VERKSTED AS

Who owns SPON VERKSTED AS?

NEXTASCENT AS is the largest registered owner, with 85.7%.

Who is the general manager of SPON VERKSTED AS?

Sven Kristian Lombardo is registered as general manager of SPON VERKSTED AS.

Where is SPON VERKSTED AS based?

SPON VERKSTED 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.