BIZTRAC BETA
Joinery installation

SPILEVEGGEN AS

Org. no. 934910486 Limited company (AS) Kristiansand Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK −41,000
Equity NOK −26,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−26k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−41k kr).

SPILEVEGGEN AS is registered as a limited company in Kristiansand, Agder with organisation number 934910486. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av interiørprodukter og alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −41,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −41,000
Equity
NOK −26,000

Financial health · 2025

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

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

Who owns SPILEVEGGEN AS?

OSCAR TØNNESLAND
SPILEVEGGEN AS
NOK 5,000 rev. · NOK −41,000 profit

SPILEVEGGEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPILEVEGGEN AS

Who owns SPILEVEGGEN AS?

OSCAR TØNNESLAND is the largest registered owner, with 60.0%.

What is the revenue of SPILEVEGGEN AS?

SPILEVEGGEN AS had revenue of NOK 5,000 in 2025.

Who is the general manager of SPILEVEGGEN AS?

Oscar Tønnesland is registered as general manager of SPILEVEGGEN AS.

Where is SPILEVEGGEN AS based?

SPILEVEGGEN AS has its business address in Kristiansand S.

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.