BIZTRAC BETA
Finishing of textiles

SPITTING IMAGE AS

Org. no. 968670557 Limited company (AS) Asker Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 43.6m
Operating profit NOK 3.7m
Equity NOK 5.8m
Incorporated 1994
Employees 24
Share capital NOK 1.2m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SPITTING IMAGE AS is registered as a limited company in Asker, Akershus with organisation number 968670557. The business is classified under finishing of textiles (NACE 13.300). The company was incorporated in 1994 and has 24 registered employees. Registered share capital is NOK 1.2m, divided into 12500 shares. The company's stated purpose is: “Handel, produksjon og foreta investeringer samt delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 43.6m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 43.6m
Operating profit
NOK 3.7m
Equity
NOK 5.8m
Est. value
NOK 17.0m

Financial health · 2024

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.0%
Good
Equity as a share of total capital

Who owns SPITTING IMAGE AS?

ART DRIVEN GROUP AS
SPITTING IMAGE AS
NOK 43.6m rev. · NOK 3.7m profit

SPITTING IMAGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPITTING IMAGE AS

Who owns SPITTING IMAGE AS?

ART DRIVEN GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of SPITTING IMAGE AS?

SPITTING IMAGE AS had revenue of NOK 43.6m in 2024.

Who is the general manager of SPITTING IMAGE AS?

Nils-Henrik Mathisen is registered as general manager of SPITTING IMAGE AS.

Where is SPITTING IMAGE AS based?

SPITTING IMAGE AS has its business address in Røyken.

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.