BIZTRAC BETA
Activities of excursion and event organisers

SCAPIN AS

Org. no. 921543581 Limited company (AS) Ullensaker Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −879,000
Equity NOK 43,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−879k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SCAPIN AS is registered as a limited company in Ullensaker, Akershus with organisation number 921543581. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Arrangere konserter, events og lignende, kjøp og salg av tilknyttede tjenester, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −879,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −879,000
Equity
NOK 43,000
Est. value
NOK 62,000

Financial health · 2024

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

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

Who owns SCAPIN AS?

TORE KVÆRNER AS
SCAPIN AS
NOK 1.0m rev. · NOK −879,000 profit

SCAPIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SCAPIN AS

Who owns SCAPIN AS?

TORE KVÆRNER AS is the largest registered owner, with 100.0%.

What is the revenue of SCAPIN AS?

SCAPIN AS had revenue of NOK 1.0m in 2024.

Where is SCAPIN AS based?

SCAPIN AS has its business address in Jessheim.

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.