BIZTRAC BETA
Computer consultancy and computer facilities management activities

SPILLE SAMMEN AS

Org. no. 933295001 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK −29,000
Equity NOK −11,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

SPILLE SAMMEN AS is registered as a limited company in Oslo, Oslo with organisation number 933295001. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby tjenester og produkter innen IKT relaterte fagområder og innen andre områder som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK −29,000
Equity
NOK −11,000

Financial health · 2025

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

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

Who owns SPILLE SAMMEN AS?

SMOKVINA HOLDING AS
SPILLE SAMMEN AS
NOK 2.7m rev. · NOK −29,000 profit

SPILLE SAMMEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPILLE SAMMEN AS

Who owns SPILLE SAMMEN AS?

SMOKVINA HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SPILLE SAMMEN AS?

SPILLE SAMMEN AS had revenue of NOK 2.7m in 2024.

Where is SPILLE SAMMEN AS based?

SPILLE SAMMEN 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.